# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2017, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-15 15:23+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Dong-gweon Oh \n"
"Language-Team: Korean (https://python.flowdas.com)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
#: ../Doc/tutorial/interpreter.rst:5
msgid "Using the Python Interpreter"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:11
msgid "Invoking the Interpreter"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:13
msgid ""
"The Python interpreter is usually installed as "
":file:`/usr/local/bin/python3.7` on those machines where it is available;"
" putting :file:`/usr/local/bin` in your Unix shell's search path makes it"
" possible to start it by typing the command:"
msgstr ""
" :file:`/usr/local/bin/python3.7` ; "
":file:`/usr/local/bin` :"
#: ../Doc/tutorial/interpreter.rst:21
msgid ""
"to the shell. [#]_ Since the choice of the directory where the "
"interpreter lives is an installation option, other places are possible; "
"check with your local Python guru or system administrator. (E.g., "
":file:`/usr/local/python` is a popular alternative location.)"
msgstr ""
" . [#]_ , "
"; . ( , "
":file:`/usr/local/python` .)"
#: ../Doc/tutorial/interpreter.rst:26
msgid ""
"On Windows machines where you have installed from the :ref:`Microsoft "
"Store `, the :file:`python3.7` command will be available. "
"If you have the :ref:`py.exe launcher ` installed, you can use "
"the :file:`py` command. See :ref:`setting-envvars` for other ways to "
"launch Python."
msgstr ""
#: ../Doc/tutorial/interpreter.rst:31
msgid ""
"Typing an end-of-file character (:kbd:`Control-D` on Unix, "
":kbd:`Control-Z` on Windows) at the primary prompt causes the interpreter"
" to exit with a zero exit status. If that doesn't work, you can exit the"
" interpreter by typing the following command: ``quit()``."
msgstr ""
" EOF(end-of-file) ( :kbd:`Control-D`, "
":kbd:`Control-Z`) , 0 . "
"``quit()`` ."
#: ../Doc/tutorial/interpreter.rst:36
msgid ""
"The interpreter's line-editing features include interactive editing, "
"history substitution and code completion on systems that support "
"readline. Perhaps the quickest check to see whether command line editing"
" is supported is typing :kbd:`Control-P` to the first Python prompt you "
"get. If it beeps, you have command line editing; see Appendix :ref:`tut-"
"interacting` for an introduction to the keys. If nothing appears to "
"happen, or if ``^P`` is echoed, command line editing isn't available; "
"you'll only be able to use backspace to remove characters from the "
"current line."
msgstr ""
" readline , , . "
" :kbd:`Control-P` . "
" ; :ref:`tut-interacting` "
". ``^P`` ; "
" ."
#: ../Doc/tutorial/interpreter.rst:45
msgid ""
"The interpreter operates somewhat like the Unix shell: when called with "
"standard input connected to a tty device, it reads and executes commands "
"interactively; when called with a file name argument or with a file as "
"standard input, it reads and executes a *script* from that file."
msgstr ""
" : tty , "
"; ."
#: ../Doc/tutorial/interpreter.rst:50
msgid ""
"A second way of starting the interpreter is ``python -c command [arg] "
"...``, which executes the statement(s) in *command*, analogous to the "
"shell's :option:`-c` option. Since Python statements often contain "
"spaces or other characters that are special to the shell, it is usually "
"advised to quote *command* in its entirety with single quotes."
msgstr ""
" ``python -c command [arg] ...`` , *command* "
" . :option:`-c` . "
" , *command* ."
#: ../Doc/tutorial/interpreter.rst:56
msgid ""
"Some Python modules are also useful as scripts. These can be invoked "
"using ``python -m module [arg] ...``, which executes the source file for "
"*module* as if you had spelled out its full name on the command line."
msgstr ""
" . ``python -m module [arg] ...`` , "
" *module* ."
#: ../Doc/tutorial/interpreter.rst:60
msgid ""
"When a script file is used, it is sometimes useful to be able to run the "
"script and enter interactive mode afterwards. This can be done by "
"passing :option:`-i` before the script."
msgstr ""
" , . "
":option:`-i` ."
#: ../Doc/tutorial/interpreter.rst:64
msgid "All command line options are described in :ref:`using-on-general`."
msgstr " :ref:`using-on-general` ."
#: ../Doc/tutorial/interpreter.rst:70
msgid "Argument Passing"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:72
msgid ""
"When known to the interpreter, the script name and additional arguments "
"thereafter are turned into a list of strings and assigned to the ``argv``"
" variable in the ``sys`` module. You can access this list by executing "
"``import sys``. The length of the list is at least one; when no script "
"and no arguments are given, ``sys.argv[0]`` is an empty string. When the"
" script name is given as ``'-'`` (meaning standard input), "
"``sys.argv[0]`` is set to ``'-'``. When :option:`-c` *command* is used, "
"``sys.argv[0]`` is set to ``'-c'``. When :option:`-m` *module* is used, "
"``sys.argv[0]`` is set to the full name of the located module. Options "
"found after :option:`-c` *command* or :option:`-m` *module* are not "
"consumed by the Python interpreter's option processing but left in "
"``sys.argv`` for the command or module to handle."
msgstr ""
" , ``sys`` ``argv`` "
". ``import sys`` . 1, "
" , ``sys.argv[0]`` . ``'-'`` ( ) "
" ``sys.argv[0]`` ``'-'`` . :option:`-c` *command* "
"``sys.argv[0]`` ``'-c'`` . :option:`-m` *module* "
"``sys.argv[0]`` . :option:`-c` *command* :option:`-m` "
"*module* ``sys.argv`` "
"."
#: ../Doc/tutorial/interpreter.rst:88
msgid "Interactive Mode"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:90
msgid ""
"When commands are read from a tty, the interpreter is said to be in "
"*interactive mode*. In this mode it prompts for the next command with "
"the *primary prompt*, usually three greater-than signs (``>>>``); for "
"continuation lines it prompts with the *secondary prompt*, by default "
"three dots (``...``). The interpreter prints a welcome message stating "
"its version number and a copyright notice before printing the first "
"prompt:"
msgstr ""
" tty , * * . * * "
" , ... (``>>>``); "
" , (``...``). "
" ."
#: ../Doc/tutorial/interpreter.rst:107
msgid ""
"Continuation lines are needed when entering a multi-line construct. As an"
" example, take a look at this :keyword:`if` statement::"
msgstr " . , :keyword:`if` ::"
#: ../Doc/tutorial/interpreter.rst:117
msgid "For more on interactive mode, see :ref:`tut-interac`."
msgstr " , :ref:`tut-interac` ."
#: ../Doc/tutorial/interpreter.rst:123
msgid "The Interpreter and Its Environment"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:129
msgid "Source Code Encoding"
msgstr " "
#: ../Doc/tutorial/interpreter.rst:131
msgid ""
"By default, Python source files are treated as encoded in UTF-8. In that"
" encoding, characters of most languages in the world can be used "
"simultaneously in string literals, identifiers and comments --- although "
"the standard library only uses ASCII characters for identifiers, a "
"convention that any portable code should follow. To display all these "
"characters properly, your editor must recognize that the file is UTF-8, "
"and it must use a font that supports all the characters in the file."
msgstr ""
", UTF-8 . "
" , , . ( ASCII "
", .) "
"UTF-8 , ."
#: ../Doc/tutorial/interpreter.rst:139
msgid ""
"To declare an encoding other than the default one, a special comment line"
" should be added as the *first* line of the file. The syntax is as "
"follows::"
msgstr " , . ::"
#: ../Doc/tutorial/interpreter.rst:144
msgid "where *encoding* is one of the valid :mod:`codecs` supported by Python."
msgstr "*encoding* (:mod:`codecs`) ."
#: ../Doc/tutorial/interpreter.rst:146
msgid ""
"For example, to declare that Windows-1252 encoding is to be used, the "
"first line of your source code file should be::"
msgstr " , Windows-1252 , ::"
#: ../Doc/tutorial/interpreter.rst:151
msgid ""
"One exception to the *first line* rule is when the source code starts "
"with a :ref:`UNIX \"shebang\" line `. In this case, the "
"encoding declaration should be added as the second line of the file. For"
" example::"
msgstr ""
" :ref:` \" (shebang)\" ` "
" . , . ::"
#: ../Doc/tutorial/interpreter.rst:159
msgid "Footnotes"
msgstr ""
#: ../Doc/tutorial/interpreter.rst:160
msgid ""
"On Unix, the Python 3.x interpreter is by default not installed with the "
"executable named ``python``, so that it does not conflict with a "
"simultaneously installed Python 2.x executable."
msgstr ""
", 3.x ``python`` , "
" 2.x ."
#~ msgid ""
#~ "On Windows machines, the Python "
#~ "installation is usually placed in "
#~ ":file:`C:\\\\Python37`, though you can change"
#~ " this when you're running the "
#~ "installer. To add this directory to "
#~ "your path, you can type the "
#~ "following command into :ref:`a command "
#~ "prompt window `::"
#~ msgstr ""
#~ ", :file:`C:\\\\Python37` "
#~ " , "
#~ ". "
#~ " :ref:` `\\ ::"