# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2022, Python Software Foundation
# This file is distributed under the same license as the Python package.
#
# Translators:
# Leon H., 2017
msgid ""
msgstr ""
"Project-Id-Version: Python 3.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-01 22:24+0800\n"
"PO-Revision-Date: 2021-07-05 14:35+0800\n"
"Last-Translator: meowmeowcat \n"
"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
"tw)\n"
"Language: zh_TW\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 3.0\n"
#: ../../tutorial/appendix.rst:5
msgid "Appendix"
msgstr ""
#: ../../tutorial/appendix.rst:11
msgid "Interactive Mode"
msgstr ""
#: ../../tutorial/appendix.rst:16
msgid "Error Handling"
msgstr ""
#: ../../tutorial/appendix.rst:18
msgid ""
"When an error occurs, the interpreter prints an error message and a stack "
"trace. In interactive mode, it then returns to the primary prompt; when "
"input came from a file, it exits with a nonzero exit status after printing "
"the stack trace. (Exceptions handled by an :keyword:`except` clause in a :"
"keyword:`try` statement are not errors in this context.) Some errors are "
"unconditionally fatal and cause an exit with a nonzero exit status; this "
"applies to internal inconsistencies and some cases of running out of "
"memory. All error messages are written to the standard error stream; normal "
"output from executed commands is written to standard output."
msgstr ""
""
" (nonzero exit "
"status) ( :keyword:`except` :keyword:`try` "
") "
""
""
#: ../../tutorial/appendix.rst:28
msgid ""
"Typing the interrupt character (usually :kbd:`Control-C` or :kbd:`Delete`) "
"to the primary or secondary prompt cancels the input and returns to the "
"primary prompt. [#]_ Typing an interrupt while a command is executing raises "
"the :exc:`KeyboardInterrupt` exception, which may be handled by a :keyword:"
"`try` statement."
msgstr ""
" :kbd:`Control-C` :kbd:"
"`Delete` [#]_ "
" :exc:`KeyboardInterrupt` :keyword:`try` "
""
#: ../../tutorial/appendix.rst:38
msgid "Executable Python Scripts"
msgstr " Python "
#: ../../tutorial/appendix.rst:40
msgid ""
"On BSD'ish Unix systems, Python scripts can be made directly executable, "
"like shell scripts, by putting the line ::"
msgstr ""
" BSD Unix Python shell "
" ::"
#: ../../tutorial/appendix.rst:43
msgid "#!/usr/bin/env python3"
msgstr "#!/usr/bin/env python3"
#: ../../tutorial/appendix.rst:45
msgid ""
"(assuming that the interpreter is on the user's :envvar:`PATH`) at the "
"beginning of the script and giving the file an executable mode. The ``#!`` "
"must be the first two characters of the file. On some platforms, this first "
"line must end with a Unix-style line ending (``'\\n'``), not a Windows "
"(``'\\r\\n'``) line ending. Note that the hash, or pound, character, "
"``'#'``, is used to start a comment in Python."
msgstr ""
" :envvar:`PATH` "
"``#!`` Unix "
"(``'\\n'``) Windows (``'\\r\\n'``) ``'#'`` "
" Python "
#: ../../tutorial/appendix.rst:52
msgid ""
"The script can be given an executable mode, or permission, using the :"
"program:`chmod` command."
msgstr " :program:`chmod` "
#: ../../tutorial/appendix.rst:55
msgid "$ chmod +x myscript.py"
msgstr "$ chmod +x myscript.py"
#: ../../tutorial/appendix.rst:59
msgid ""
"On Windows systems, there is no notion of an \"executable mode\". The "
"Python installer automatically associates ``.py`` files with ``python.exe`` "
"so that a double-click on a Python file will run it as a script. The "
"extension can also be ``.pyw``, in that case, the console window that "
"normally appears is suppressed."
msgstr ""
" Windows Python ``."
"py`` ``python.exe`` Python "
" ``.pyw``"
#: ../../tutorial/appendix.rst:69
msgid "The Interactive Startup File"
msgstr ""
#: ../../tutorial/appendix.rst:71
msgid ""
"When you use Python interactively, it is frequently handy to have some "
"standard commands executed every time the interpreter is started. You can "
"do this by setting an environment variable named :envvar:`PYTHONSTARTUP` to "
"the name of a file containing your start-up commands. This is similar to "
"the :file:`.profile` feature of the Unix shells."
msgstr ""
" Python "
" :envvar:`PYTHONSTARTUP` "
" Unix shell :file:`.profile` "
#: ../../tutorial/appendix.rst:77
msgid ""
"This file is only read in interactive sessions, not when Python reads "
"commands from a script, and not when :file:`/dev/tty` is given as the "
"explicit source of commands (which otherwise behaves like an interactive "
"session). It is executed in the same namespace where interactive commands "
"are executed, so that objects that it defines or imports can be used without "
"qualification in the interactive session. You can also change the prompts "
"``sys.ps1`` and ``sys.ps2`` in this file."
msgstr ""
" Python "
" :file:`/dev/tty` "
" import "
" ``sys.ps1`` ``sys.ps2`` "
""
#: ../../tutorial/appendix.rst:85
msgid ""
"If you want to read an additional start-up file from the current directory, "
"you can program this in the global start-up file using code like ``if os."
"path.isfile('.pythonrc.py'): exec(open('.pythonrc.py').read())``. If you "
"want to use the startup file in a script, you must do this explicitly in the "
"script::"
msgstr ""
" "
"``if os.path.isfile('.pythonrc.py'): exec(open('.pythonrc.py').read()`` "
""
" ::"
#: ../../tutorial/appendix.rst:91
msgid ""
"import os\n"
"filename = os.environ.get('PYTHONSTARTUP')\n"
"if filename and os.path.isfile(filename):\n"
" with open(filename) as fobj:\n"
" startup_file = fobj.read()\n"
" exec(startup_file)"
msgstr ""
"import os\n"
"filename = os.environ.get('PYTHONSTARTUP')\n"
"if filename and os.path.isfile(filename):\n"
" with open(filename) as fobj:\n"
" startup_file = fobj.read()\n"
" exec(startup_file)"
#: ../../tutorial/appendix.rst:102
msgid "The Customization Modules"
msgstr ""
#: ../../tutorial/appendix.rst:104
msgid ""
"Python provides two hooks to let you customize it: :index:`sitecustomize` "
"and :index:`usercustomize`. To see how it works, you need first to find the "
"location of your user site-packages directory. Start Python and run this "
"code::"
msgstr ""
"Python (hook) :index:`sitecustomize` :"
"index:`usercustomize` site-packages "
" Python ::"
#: ../../tutorial/appendix.rst:108
msgid ""
">>> import site\n"
">>> site.getusersitepackages()\n"
"'/home/user/.local/lib/python3.x/site-packages'"
msgstr ""
">>> import site\n"
">>> site.getusersitepackages()\n"
"'/home/user/.local/lib/python3.x/site-packages'"
#: ../../tutorial/appendix.rst:112
msgid ""
"Now you can create a file named :file:`usercustomize.py` in that directory "
"and put anything you want in it. It will affect every invocation of Python, "
"unless it is started with the :option:`-s` option to disable the automatic "
"import."
msgstr ""
" :file:`usercustomize.py` "
" Python :option:`-s` "
" import "
#: ../../tutorial/appendix.rst:116
msgid ""
":index:`sitecustomize` works in the same way, but is typically created by an "
"administrator of the computer in the global site-packages directory, and is "
"imported before :index:`usercustomize`. See the documentation of the :mod:"
"`site` module for more details."
msgstr ""
":index:`sitecustomize` site-"
"packages :index:`usercustomize` import "
" :mod:`site` "
#: ../../tutorial/appendix.rst:123
msgid "Footnotes"
msgstr ""
#: ../../tutorial/appendix.rst:124
msgid "A problem with the GNU Readline package may prevent this."
msgstr "GNU Readline "