python-docs-ko/faq/windows.po at 3.6 · python/python-docs-ko · GitHub

Repository navigation

History

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409

410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441

442

443

444

445

446

447

448

449

450

451

452

453

454

455

456

457

458

459

460

461

462

463

464

465

466

467

468

469

470

471

472

473

474

475

476

477

478

479

480

481

482

483

484

485

486

487

488

489

490

491

492

493

494

495

496

497

498

499

500

501

502

503

504

505

# SOME DESCRIPTIVE TITLE.

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.6\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2018-05-26 11:10+0900\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: LANGUAGE <LL@li.org>\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=utf-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Generated-By: Babel 2.5.1\n"

#: ../Doc/faq/windows.rst:9

msgid "Python on Windows FAQ"

msgstr ""

#: ../Doc/faq/windows.rst:20

msgid "How do I run a Python program under Windows?"

msgstr ""

#: ../Doc/faq/windows.rst:22

msgid ""

"This is not necessarily a straightforward question. If you are already "

"familiar with running programs from the Windows command line then "

"everything will seem obvious; otherwise, you might need a little more "

"guidance."

msgstr ""

#: ../Doc/faq/windows.rst:29

msgid ""

"This series of screencasts aims to get you up and running with Python on "

"Windows XP. The knowledge is distilled into 1.5 hours and will get you "

"up and running with the right Python distribution, coding in your choice "

"of IDE, and debugging and writing solid code with unit-tests."

msgstr ""

#: ../Doc/faq/windows.rst:38

msgid ""

"Unless you use some sort of integrated development environment, you will "

"end up *typing* Windows commands into what is variously referred to as a "

"\"DOS window\" or \"Command prompt window\". Usually you can create such"

" a window from your Start menu; under Windows 7 the menu selection is "

":menuselection:`Start --> Programs --> Accessories --> Command Prompt`. "

"You should be able to recognize when you have started such a window "

"because you will see a Windows \"command prompt\", which usually looks "

"like this:"

msgstr ""

#: ../Doc/faq/windows.rst:50

msgid ""

"The letter may be different, and there might be other things after it, so"

" you might just as easily see something like:"

msgstr ""

#: ../Doc/faq/windows.rst:57

msgid ""

"depending on how your computer has been set up and what else you have "

"recently done with it. Once you have started such a window, you are well"

" on the way to running Python programs."

msgstr ""

#: ../Doc/faq/windows.rst:61

msgid ""

"You need to realize that your Python scripts have to be processed by "

"another program called the Python *interpreter*. The interpreter reads "

"your script, compiles it into bytecodes, and then executes the bytecodes "

"to run your program. So, how do you arrange for the interpreter to handle"

" your Python?"

msgstr ""

#: ../Doc/faq/windows.rst:66

msgid ""

"First, you need to make sure that your command window recognises the word"

" \"python\" as an instruction to start the interpreter. If you have "

"opened a command window, you should try entering the command ``python`` "

"and hitting return:"

msgstr ""

#: ../Doc/faq/windows.rst:75

msgid "You should then see something like:"

msgstr ""

#: ../Doc/faq/windows.rst:83

msgid ""

"You have started the interpreter in \"interactive mode\". That means you "

"can enter Python statements or expressions interactively and have them "

"executed or evaluated while you wait. This is one of Python's strongest "

"features. Check it by entering a few expressions of your choice and "

"seeing the results:"

msgstr ""

#: ../Doc/faq/windows.rst:95

msgid ""

"Many people use the interactive mode as a convenient yet highly "

"programmable calculator. When you want to end your interactive Python "

"session, hold the :kbd:`Ctrl` key down while you enter a :kbd:`Z`, then "

"hit the \":kbd:`Enter`\" key to get back to your Windows command prompt."

msgstr ""

#: ../Doc/faq/windows.rst:100

msgid ""

"You may also find that you have a Start-menu entry such as "

":menuselection:`Start --> Programs --> Python 3.3 --> Python (command "

"line)` that results in you seeing the ``>>>`` prompt in a new window. If"

" so, the window will disappear after you enter the :kbd:`Ctrl-Z` "

"character; Windows is running a single \"python\" command in the window, "

"and closes it when you terminate the interpreter."

msgstr ""

#: ../Doc/faq/windows.rst:106

msgid ""

"If the ``python`` command, instead of displaying the interpreter prompt "

"``>>>``, gives you a message like::"

msgstr ""

#: ../Doc/faq/windows.rst:114

msgid ""

"Python is not added to the DOS path by default. This screencast will "

"walk you through the steps to add the correct entry to the `System Path`,"

" allowing Python to be executed from the command-line by all users."

msgstr ""

#: ../Doc/faq/windows.rst:123

msgid "or::"

msgstr ""

#: ../Doc/faq/windows.rst:127

msgid ""

"then you need to make sure that your computer knows where to find the "

"Python interpreter. To do this you will have to modify a setting called "

"PATH, which is a list of directories where Windows will look for "

"programs."

msgstr ""

#: ../Doc/faq/windows.rst:131

msgid ""

"You should arrange for Python's installation directory to be added to the"

" PATH of every command window as it starts. If you installed Python "

"fairly recently then the command ::"

msgstr ""

#: ../Doc/faq/windows.rst:137

msgid ""

"will probably tell you where it is installed; the usual location is "

"something like ``C:\\Python33``. Otherwise you will be reduced to a "

"search of your whole disk ... use :menuselection:`Tools --> Find` or hit "

"the :guilabel:`Search` button and look for \"python.exe\". Supposing you"

" discover that Python is installed in the ``C:\\Python33`` directory (the"

" default at the time of writing), you should make sure that entering the "

"command ::"

msgstr ""

#: ../Doc/faq/windows.rst:146

msgid ""

"starts up the interpreter as above (and don't forget you'll need a "

"\":kbd:`Ctrl-Z`\" and an \":kbd:`Enter`\" to get out of it). Once you "

"have verified the directory, you can add it to the system path to make it"

" easier to start Python by just running the ``python`` command. This is "

"currently an option in the installer as of CPython 3.3."

msgstr ""

#: ../Doc/faq/windows.rst:152

msgid ""

"More information about environment variables can be found on the "

":ref:`Using Python on Windows <setting-envvars>` page."

msgstr ""

#: ../Doc/faq/windows.rst:156

msgid "How do I make Python scripts executable?"

msgstr ""

#: ../Doc/faq/windows.rst:158

msgid ""

"On Windows, the standard Python installer already associates the .py "

"extension with a file type (Python.File) and gives that file type an open"

" command that runs the interpreter (``D:\\Program "

"Files\\Python\\python.exe \"%1\" %*``). This is enough to make scripts "

"executable from the command prompt as 'foo.py'. If you'd rather be able "

"to execute the script by simple typing 'foo' with no extension you need "

"to add .py to the PATHEXT environment variable."

msgstr ""

#: ../Doc/faq/windows.rst:166

msgid "Why does Python sometimes take so long to start?"

msgstr ""

#: ../Doc/faq/windows.rst:168

msgid ""

"Usually Python starts very quickly on Windows, but occasionally there are"

" bug reports that Python suddenly begins to take a long time to start up."

" This is made even more puzzling because Python will work fine on other "

"Windows systems which appear to be configured identically."

msgstr ""

#: ../Doc/faq/windows.rst:173

msgid ""

"The problem may be caused by a misconfiguration of virus checking "

"software on the problem machine. Some virus scanners have been known to "

"introduce startup overhead of two orders of magnitude when the scanner is"

" configured to monitor all reads from the filesystem. Try checking the "

"configuration of virus scanning software on your systems to ensure that "

"they are indeed configured identically. McAfee, when configured to scan "

"all file system read activity, is a particular offender."

msgstr ""

#: ../Doc/faq/windows.rst:183

msgid "How do I make an executable from a Python script?"

msgstr ""

#: ../Doc/faq/windows.rst:185

msgid ""

"See http://cx-freeze.sourceforge.net/ for a distutils extension that "

"allows you to create console and GUI executables from Python code. "

"`py2exe <http://www.py2exe.org/>`_, the most popular extension for "

"building Python 2.x-based executables, does not yet support Python 3 but "

"a version that does is in development."

msgstr ""

#: ../Doc/faq/windows.rst:193

msgid "Is a ``*.pyd`` file the same as a DLL?"

msgstr ""

#: ../Doc/faq/windows.rst:195

msgid ""

"Yes, .pyd files are dll's, but there are a few differences. If you have "

"a DLL named ``foo.pyd``, then it must have a function ``PyInit_foo()``. "

"You can then write Python \"import foo\", and Python will search for "

"foo.pyd (as well as foo.py, foo.pyc) and if it finds it, will attempt to "

"call ``PyInit_foo()`` to initialize it. You do not link your .exe with "

"foo.lib, as that would cause Windows to require the DLL to be present."

msgstr ""

#: ../Doc/faq/windows.rst:202

msgid ""

"Note that the search path for foo.pyd is PYTHONPATH, not the same as the "

"path that Windows uses to search for foo.dll. Also, foo.pyd need not be "

"present to run your program, whereas if you linked your program with a "

"dll, the dll is required. Of course, foo.pyd is required if you want to "

"say ``import foo``. In a DLL, linkage is declared in the source code "

"with ``__declspec(dllexport)``. In a .pyd, linkage is defined in a list "

"of available functions."

msgstr ""

#: ../Doc/faq/windows.rst:211

msgid "How can I embed Python into a Windows application?"

msgstr ""

#: ../Doc/faq/windows.rst:213

msgid ""

"Embedding the Python interpreter in a Windows app can be summarized as "

"follows:"

msgstr ""

#: ../Doc/faq/windows.rst:215

msgid ""

"Do _not_ build Python into your .exe file directly. On Windows, Python "

"must be a DLL to handle importing modules that are themselves DLL's. "

"(This is the first key undocumented fact.) Instead, link to "

":file:`python{NN}.dll`; it is typically installed in "

"``C:\\Windows\\System``. *NN* is the Python version, a number such as "

"\"33\" for Python 3.3."

msgstr ""

#: ../Doc/faq/windows.rst:221

msgid ""

"You can link to Python in two different ways. Load-time linking means "

"linking against :file:`python{NN}.lib`, while run-time linking means "

"linking against :file:`python{NN}.dll`. (General note: "

":file:`python{NN}.lib` is the so-called \"import lib\" corresponding to "

":file:`python{NN}.dll`. It merely defines symbols for the linker.)"

msgstr ""

#: ../Doc/faq/windows.rst:227

msgid ""

"Run-time linking greatly simplifies link options; everything happens at "

"run time. Your code must load :file:`python{NN}.dll` using the Windows "

"``LoadLibraryEx()`` routine. The code must also use access routines and "

"data in :file:`python{NN}.dll` (that is, Python's C API's) using pointers"

" obtained by the Windows ``GetProcAddress()`` routine. Macros can make "

"using these pointers transparent to any C code that calls routines in "

"Python's C API."

msgstr ""

#: ../Doc/faq/windows.rst:234

msgid ""

"Borland note: convert :file:`python{NN}.lib` to OMF format using "

"Coff2Omf.exe first."

msgstr ""

#: ../Doc/faq/windows.rst:239

msgid ""

"If you use SWIG, it is easy to create a Python \"extension module\" that "

"will make the app's data and methods available to Python. SWIG will "

"handle just about all the grungy details for you. The result is C code "

"that you link *into* your .exe file (!) You do _not_ have to create a "

"DLL file, and this also simplifies linking."

msgstr ""

#: ../Doc/faq/windows.rst:245

msgid ""

"SWIG will create an init function (a C function) whose name depends on "

"the name of the extension module. For example, if the name of the module"

" is leo, the init function will be called initleo(). If you use SWIG "

"shadow classes, as you should, the init function will be called "

"initleoc(). This initializes a mostly hidden helper class used by the "

"shadow class."

msgstr ""

#: ../Doc/faq/windows.rst:251

msgid ""

"The reason you can link the C code in step 2 into your .exe file is that "

"calling the initialization function is equivalent to importing the module"

" into Python! (This is the second key undocumented fact.)"

msgstr ""

#: ../Doc/faq/windows.rst:255

msgid ""

"In short, you can use the following code to initialize the Python "

"interpreter with your extension module."

msgstr ""

#: ../Doc/faq/windows.rst:266

msgid ""

"There are two problems with Python's C API which will become apparent if "

"you use a compiler other than MSVC, the compiler used to build "

"pythonNN.dll."

msgstr ""

#: ../Doc/faq/windows.rst:269

msgid ""

"Problem 1: The so-called \"Very High Level\" functions that take FILE * "

"arguments will not work in a multi-compiler environment because each "

"compiler's notion of a struct FILE will be different. From an "

"implementation standpoint these are very _low_ level functions."

msgstr ""

#: ../Doc/faq/windows.rst:274

msgid ""

"Problem 2: SWIG generates the following code when generating wrappers to "

"void functions:"

msgstr ""

#: ../Doc/faq/windows.rst:283

msgid ""

"Alas, Py_None is a macro that expands to a reference to a complex data "

"structure called _Py_NoneStruct inside pythonNN.dll. Again, this code "

"will fail in a mult-compiler environment. Replace such code by:"

msgstr ""

#: ../Doc/faq/windows.rst:291

msgid ""

"It may be possible to use SWIG's ``%typemap`` command to make the change "

"automatically, though I have not been able to get this to work (I'm a "

"complete SWIG newbie)."

msgstr ""

#: ../Doc/faq/windows.rst:295

msgid ""

"Using a Python shell script to put up a Python interpreter window from "

"inside your Windows app is not a good idea; the resulting window will be "

"independent of your app's windowing system. Rather, you (or the "

"wxPythonWindow class) should create a \"native\" interpreter window. It "

"is easy to connect that window to the Python interpreter. You can "

"redirect Python's i/o to _any_ object that supports read and write, so "

"all you need is a Python object (defined in your extension module) that "

"contains read() and write() methods."

msgstr ""

#: ../Doc/faq/windows.rst:304

msgid "How do I keep editors from inserting tabs into my Python source?"

msgstr ""

#: ../Doc/faq/windows.rst:306

msgid ""

"The FAQ does not recommend using tabs, and the Python style guide, "

":pep:`8`, recommends 4 spaces for distributed Python code; this is also "

"the Emacs python-mode default."

msgstr ""

#: ../Doc/faq/windows.rst:310

msgid ""

"Under any editor, mixing tabs and spaces is a bad idea. MSVC is no "

"different in this respect, and is easily configured to use spaces: Take "

":menuselection:`Tools --> Options --> Tabs`, and for file type "

"\"Default\" set \"Tab size\" and \"Indent size\" to 4, and select the "

"\"Insert spaces\" radio button."

msgstr ""

#: ../Doc/faq/windows.rst:315

msgid ""

"Python raises :exc:`IndentationError` or :exc:`TabError` if mixed tabs "

"and spaces are causing problems in leading whitespace. You may also run "

"the :mod:`tabnanny` module to check a directory tree in batch mode."

msgstr ""

#: ../Doc/faq/windows.rst:322

msgid "How do I check for a keypress without blocking?"

msgstr ""

#: ../Doc/faq/windows.rst:324

msgid ""

"Use the msvcrt module. This is a standard Windows-specific extension "

"module. It defines a function ``kbhit()`` which checks whether a keyboard"

" hit is present, and ``getch()`` which gets one character without echoing"

" it."

msgstr ""

#: ../Doc/faq/windows.rst:330

msgid "How do I emulate os.kill() in Windows?"

msgstr ""

#: ../Doc/faq/windows.rst:332

msgid ""

"Prior to Python 2.7 and 3.2, to terminate a process, you can use "

":mod:`ctypes`:"

msgstr ""

#: ../Doc/faq/windows.rst:344

msgid ""

"In 2.7 and 3.2, :func:`os.kill` is implemented similar to the above "

"function, with the additional feature of being able to send :kbd:`Ctrl+C`"

" and :kbd:`Ctrl+Break` to console subprocesses which are designed to "

"handle those signals. See :func:`os.kill` for further details."

msgstr ""

#: ../Doc/faq/windows.rst:350

msgid "How do I extract the downloaded documentation on Windows?"

msgstr ""

#: ../Doc/faq/windows.rst:352

msgid ""

"Sometimes, when you download the documentation package to a Windows "

"machine using a web browser, the file extension of the saved file ends up"

" being .EXE. This is a mistake; the extension should be .TGZ."

msgstr ""

#: ../Doc/faq/windows.rst:356

msgid ""

"Simply rename the downloaded file to have the .TGZ extension, and WinZip "

"will be able to handle it. (If your copy of WinZip doesn't, get a newer "

"one from https://www.winzip.com.)"

msgstr ""

#~ msgid ""

#~ "Unless you use some sort of "

#~ "integrated development environment, you will"

#~ " end up *typing* Windows commands "

#~ "into what is variously referred to "

#~ "as a \"DOS window\" or \"Command "

#~ "prompt window\". Usually you can create"

#~ " such a window from your Start "

#~ "menu; under Windows 7 the menu "

#~ "selection is :menuselection:`Start --> "

#~ "Programs --> Accessories --> Command "

#~ "Prompt`. You should be able to "

#~ "recognize when you have started such "

#~ "a window because you will see a"

#~ " Windows \"command prompt\", which usually"

#~ " looks like this::"

#~ msgstr ""

#~ msgid ""

#~ "The letter may be different, and "

#~ "there might be other things after "

#~ "it, so you might just as easily"

#~ " see something like::"

#~ msgstr ""

#~ msgid ""

#~ "First, you need to make sure that"

#~ " your command window recognises the "

#~ "word \"python\" as an instruction to "

#~ "start the interpreter. If you have "

#~ "opened a command window, you should "

#~ "try entering the command ``python`` and"

#~ " hitting return.::"

#~ msgstr ""

#~ msgid "You should then see something like::"

#~ msgstr ""

#~ msgid ""

#~ "You have started the interpreter in "

#~ "\"interactive mode\". That means you can"

#~ " enter Python statements or expressions "

#~ "interactively and have them executed or"

#~ " evaluated while you wait. This is"

#~ " one of Python's strongest features. "

#~ "Check it by entering a few "

#~ "expressions of your choice and seeing"

#~ " the results::"

#~ msgstr ""

#~ msgid ""

#~ "Prior to Python 2.7 and 3.2, to"

#~ " terminate a process, you can use "

#~ ":mod:`ctypes`::"

#~ msgstr ""

python-docs-ko/faq/windows.po at 3.6 · python/python-docs-ko · GitHub

Repository navigation

Expand file tree

Breadcrumbs

windows.po

Latest commit

History

Breadcrumbs

windows.po

File metadata and controls