forked from AFPy/python-docs-fr
Hi, gettext_compact=0.
This commit is contained in:
parent 4d36dfa0db
commit 84e5545ebb
476 changed files with 296413 additions and 283327 deletions
1425 faq/design.po Normal file
1425
faq/design.po Normal file File diff suppressed because it is too large Load diff
387 faq/extending.po Normal file
387
faq/extending.po Normal file | | @ -0,0 +1,387 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/extending.rst:3 | ||||
msgid "Extending/Embedding FAQ" | ||||
msgstr "FAQ Extension/Intégration" | ||||
| ||||
#: ../Doc/faq/extending.rst:16 | ||||
msgid "Can I create my own functions in C?" | ||||
msgstr "Puis-je créer mes propres fonctions en C ?" | ||||
| ||||
#: ../Doc/faq/extending.rst:18 | ||||
msgid "" | ||||
"Yes, you can create built-in modules containing functions, variables, " | ||||
"exceptions and even new types in C. This is explained in the document :ref:" | ||||
"`extending-index`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:22 | ||||
msgid "Most intermediate or advanced Python books will also cover this topic." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:26 | ||||
msgid "Can I create my own functions in C++?" | ||||
msgstr "Puis-je créer mes propres fonctions en C++ ?" | ||||
| ||||
#: ../Doc/faq/extending.rst:28 | ||||
msgid "" | ||||
"Yes, using the C compatibility features found in C++. Place ``extern \"C" | ||||
"\" { ... }`` around the Python include files and put ``extern \"C\"`` before " | ||||
"each function that is going to be called by the Python interpreter. Global " | ||||
"or static C++ objects with constructors are probably not a good idea." | ||||
msgstr "" | ||||
"Oui, en utilisant les fonctionnalités de compatibilité C existantes en C++. " | ||||
"Placez ``extern \"C\" { ... }`` autour des fichiers Python inclus et mettez " | ||||
"``extern \"C\"`` avant chaque fonction qui va être appelée par " | ||||
"l'interpréteur Python. Les objets C++ globaux ou statiques avec les " | ||||
"constructeurs ne sont probablement pas une bonne idée." | ||||
| ||||
#: ../Doc/faq/extending.rst:37 | ||||
msgid "Writing C is hard; are there any alternatives?" | ||||
msgstr "Écrire directement en C est difficile ; existe-t-il des alternatives ?" | ||||
| ||||
#: ../Doc/faq/extending.rst:39 | ||||
msgid "" | ||||
"There are a number of alternatives to writing your own C extensions, " | ||||
"depending on what you're trying to do." | ||||
msgstr "" | ||||
"Il y a un certain nombre de solutions existantes qui vous permettent " | ||||
"d'écrire vos propres extensions C, selon ce que vous essayez de faire." | ||||
| ||||
#: ../Doc/faq/extending.rst:44 | ||||
msgid "" | ||||
"`Cython <http://cython.org>`_ and its relative `Pyrex <https://www.cosc." | ||||
"canterbury.ac.nz/greg.ewing/python/Pyrex/>`_ are compilers that accept a " | ||||
"slightly modified form of Python and generate the corresponding C code. " | ||||
"Cython and Pyrex make it possible to write an extension without having to " | ||||
"learn Python's C API." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:50 | ||||
msgid "" | ||||
"If you need to interface to some C or C++ library for which no Python " | ||||
"extension currently exists, you can try wrapping the library's data types " | ||||
"and functions with a tool such as `SWIG <http://www.swig.org>`_. `SIP " | ||||
"<https://riverbankcomputing.com/software/sip/intro>`__, `CXX <http://cxx." | ||||
"sourceforge.net/>`_ `Boost <http://www.boost.org/libs/python/doc/index." | ||||
"html>`_, or `Weave <https://scipy.github.io/devdocs/tutorial/weave.html>`_ " | ||||
"are also alternatives for wrapping C++ libraries." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:61 | ||||
msgid "How can I execute arbitrary Python statements from C?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:63 | ||||
msgid "" | ||||
"The highest-level function to do this is :c:func:`PyRun_SimpleString` which " | ||||
"takes a single string argument to be executed in the context of the module " | ||||
"``__main__`` and returns 0 for success and -1 when an exception occurred " | ||||
"(including ``SyntaxError``). If you want more control, use :c:func:" | ||||
"`PyRun_String`; see the source for :c:func:`PyRun_SimpleString` in ``Python/" | ||||
"pythonrun.c``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:72 | ||||
msgid "How can I evaluate an arbitrary Python expression from C?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:74 | ||||
msgid "" | ||||
"Call the function :c:func:`PyRun_String` from the previous question with the " | ||||
"start symbol :c:data:`Py_eval_input`; it parses an expression, evaluates it " | ||||
"and returns its value." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:80 | ||||
msgid "How do I extract C values from a Python object?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:82 | ||||
msgid "" | ||||
"That depends on the object's type. If it's a tuple, :c:func:`PyTuple_Size` " | ||||
"returns its length and :c:func:`PyTuple_GetItem` returns the item at a " | ||||
"specified index. Lists have similar functions, :c:func:`PyListSize` and :c:" | ||||
"func:`PyList_GetItem`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:87 | ||||
msgid "" | ||||
"For bytes, :c:func:`PyBytes_Size` returns its length and :c:func:" | ||||
"`PyBytes_AsStringAndSize` provides a pointer to its value and its length. " | ||||
"Note that Python bytes objects may contain null bytes so C's :c:func:" | ||||
"`strlen` should not be used." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:92 | ||||
msgid "" | ||||
"To test the type of an object, first make sure it isn't *NULL*, and then " | ||||
"use :c:func:`PyBytes_Check`, :c:func:`PyTuple_Check`, :c:func:" | ||||
"`PyList_Check`, etc." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:95 | ||||
msgid "" | ||||
"There is also a high-level API to Python objects which is provided by the so-" | ||||
"called 'abstract' interface -- read ``Include/abstract.h`` for further " | ||||
"details. It allows interfacing with any kind of Python sequence using calls " | ||||
"like :c:func:`PySequence_Length`, :c:func:`PySequence_GetItem`, etc. as well " | ||||
"as many other useful protocols such as numbers (:c:func:`PyNumber_Index` et " | ||||
"al.) and mappings in the PyMapping APIs." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:104 | ||||
msgid "How do I use Py_BuildValue() to create a tuple of arbitrary length?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:106 | ||||
msgid "You can't. Use :c:func:`PyTuple_Pack` instead." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:110 | ||||
msgid "How do I call an object's method from C?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:112 | ||||
msgid "" | ||||
"The :c:func:`PyObject_CallMethod` function can be used to call an arbitrary " | ||||
"method of an object. The parameters are the object, the name of the method " | ||||
"to call, a format string like that used with :c:func:`Py_BuildValue`, and " | ||||
"the argument values::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:121 | ||||
msgid "" | ||||
"This works for any object that has methods -- whether built-in or user-" | ||||
"defined. You are responsible for eventually :c:func:`Py_DECREF`\\ 'ing the " | ||||
"return value." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:124 | ||||
msgid "" | ||||
"To call, e.g., a file object's \"seek\" method with arguments 10, 0 " | ||||
"(assuming the file object pointer is \"f\")::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:135 | ||||
msgid "" | ||||
"Note that since :c:func:`PyObject_CallObject` *always* wants a tuple for the " | ||||
"argument list, to call a function without arguments, pass \"()\" for the " | ||||
"format, and to call a function with one argument, surround the argument in " | ||||
"parentheses, e.g. \"(i)\"." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:142 | ||||
msgid "" | ||||
"How do I catch the output from PyErr_Print() (or anything that prints to " | ||||
"stdout/stderr)?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:144 | ||||
msgid "" | ||||
"In Python code, define an object that supports the ``write()`` method. " | ||||
"Assign this object to :data:`sys.stdout` and :data:`sys.stderr`. Call " | ||||
"print_error, or just allow the standard traceback mechanism to work. Then, " | ||||
"the output will go wherever your ``write()`` method sends it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:149 | ||||
msgid "The easiest way to do this is to use the :class:`io.StringIO` class:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:161 | ||||
msgid "A custom object to do the same would look like this:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:182 | ||||
msgid "How do I access a module written in Python from C?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:184 | ||||
msgid "You can get a pointer to the module object as follows::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:188 | ||||
msgid "" | ||||
"If the module hasn't been imported yet (i.e. it is not yet present in :data:" | ||||
"`sys.modules`), this initializes the module; otherwise it simply returns the " | ||||
"value of ``sys.modules[\"<modulename>\"]``. Note that it doesn't enter the " | ||||
"module into any namespace -- it only ensures it has been initialized and is " | ||||
"stored in :data:`sys.modules`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:194 | ||||
msgid "" | ||||
"You can then access the module's attributes (i.e. any name defined in the " | ||||
"module) as follows::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:199 | ||||
msgid "" | ||||
"Calling :c:func:`PyObject_SetAttrString` to assign to variables in the " | ||||
"module also works." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:204 | ||||
msgid "How do I interface to C++ objects from Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:206 | ||||
msgid "" | ||||
"Depending on your requirements, there are many approaches. To do this " | ||||
"manually, begin by reading :ref:`the \"Extending and Embedding\" document " | ||||
"<extending-index>`. Realize that for the Python run-time system, there " | ||||
"isn't a whole lot of difference between C and C++ -- so the strategy of " | ||||
"building a new Python type around a C structure (pointer) type will also " | ||||
"work for C++ objects." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:212 | ||||
msgid "For C++ libraries, see :ref:`c-wrapper-software`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:216 | ||||
msgid "I added a module using the Setup file and the make fails; why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:218 | ||||
msgid "" | ||||
"Setup must end in a newline, if there is no newline there, the build process " | ||||
"fails. (Fixing this requires some ugly shell script hackery, and this bug " | ||||
"is so minor that it doesn't seem worth the effort.)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:224 | ||||
msgid "How do I debug an extension?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:226 | ||||
msgid "" | ||||
"When using GDB with dynamically loaded extensions, you can't set a " | ||||
"breakpoint in your extension until your extension is loaded." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:229 | ||||
msgid "In your ``.gdbinit`` file (or interactively), add the command:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:235 | ||||
msgid "Then, when you run GDB:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:247 | ||||
msgid "" | ||||
"I want to compile a Python module on my Linux system, but some files are " | ||||
"missing. Why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:249 | ||||
msgid "" | ||||
"Most packaged versions of Python don't include the :file:`/usr/lib/python2." | ||||
"{x}/config/` directory, which contains various files required for compiling " | ||||
"Python extensions." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:253 | ||||
msgid "For Red Hat, install the python-devel RPM to get the necessary files." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:255 | ||||
msgid "For Debian, run ``apt-get install python-dev``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:259 | ||||
msgid "How do I tell \"incomplete input\" from \"invalid input\"?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:261 | ||||
msgid "" | ||||
"Sometimes you want to emulate the Python interactive interpreter's behavior, " | ||||
"where it gives you a continuation prompt when the input is incomplete (e.g. " | ||||
"you typed the start of an \"if\" statement or you didn't close your " | ||||
"parentheses or triple string quotes), but it gives you a syntax error " | ||||
"message immediately when the input is invalid." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:267 | ||||
msgid "" | ||||
"In Python you can use the :mod:`codeop` module, which approximates the " | ||||
"parser's behavior sufficiently. IDLE uses this, for example." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:270 | ||||
msgid "" | ||||
"The easiest way to do it in C is to call :c:func:`PyRun_InteractiveLoop` " | ||||
"(perhaps in a separate thread) and let the Python interpreter handle the " | ||||
"input for you. You can also set the :c:func:`PyOS_ReadlineFunctionPointer` " | ||||
"to point at your custom input function. See ``Modules/readline.c`` and " | ||||
"``Parser/myreadline.c`` for more hints." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:276 | ||||
msgid "" | ||||
"However sometimes you have to run the embedded Python interpreter in the " | ||||
"same thread as your rest application and you can't allow the :c:func:" | ||||
"`PyRun_InteractiveLoop` to stop while waiting for user input. The one " | ||||
"solution then is to call :c:func:`PyParser_ParseString` and test for ``e." | ||||
"error`` equal to ``E_EOF``, which means the input is incomplete). Here's a " | ||||
"sample code fragment, untested, inspired by code from Alex Farber::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:309 | ||||
msgid "" | ||||
"Another solution is trying to compile the received string with :c:func:" | ||||
"`Py_CompileString`. If it compiles without errors, try to execute the " | ||||
"returned code object by calling :c:func:`PyEval_EvalCode`. Otherwise save " | ||||
"the input for later. If the compilation fails, find out if it's an error or " | ||||
"just more input is required - by extracting the message string from the " | ||||
"exception tuple and comparing it to the string \"unexpected EOF while parsing" | ||||
"\". Here is a complete example using the GNU readline library (you may want " | ||||
"to ignore **SIGINT** while calling readline())::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:430 | ||||
msgid "How do I find undefined g++ symbols __builtin_new or __pure_virtual?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:432 | ||||
msgid "" | ||||
"To dynamically load g++ extension modules, you must recompile Python, relink " | ||||
"it using g++ (change LINKCC in the Python Modules Makefile), and link your " | ||||
"extension module using g++ (e.g., ``g++ -shared -o mymodule.so mymodule.o``)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:438 | ||||
msgid "" | ||||
"Can I create an object class with some methods implemented in C and others " | ||||
"in Python (e.g. through inheritance)?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:440 | ||||
msgid "" | ||||
"Yes, you can inherit from built-in classes such as :class:`int`, :class:" | ||||
"`list`, :class:`dict`, etc." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/extending.rst:443 | ||||
msgid "" | ||||
"The Boost Python Library (BPL, http://www.boost.org/libs/python/doc/index." | ||||
"html) provides a way of doing this from C++ (i.e. you can inherit from an " | ||||
"extension class written in C++ using the BPL)." | ||||
msgstr "" | ||||
636 faq/general.po Normal file
636
faq/general.po Normal file | | @ -0,0 +1,636 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/general.rst:5 | ||||
msgid "General Python FAQ" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:13 | ||||
msgid "General Information" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:16 | ||||
msgid "What is Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:18 | ||||
msgid "" | ||||
"Python is an interpreted, interactive, object-oriented programming " | ||||
"language. It incorporates modules, exceptions, dynamic typing, very high " | ||||
"level dynamic data types, and classes. Python combines remarkable power " | ||||
"with very clear syntax. It has interfaces to many system calls and " | ||||
"libraries, as well as to various window systems, and is extensible in C or C+" | ||||
"+. It is also usable as an extension language for applications that need a " | ||||
"programmable interface. Finally, Python is portable: it runs on many Unix " | ||||
"variants, on the Mac, and on Windows 2000 and later." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:27 | ||||
msgid "" | ||||
"To find out more, start with :ref:`tutorial-index`. The `Beginner's Guide " | ||||
"to Python <https://wiki.python.org/moin/BeginnersGuide>`_ links to other " | ||||
"introductory tutorials and resources for learning Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:33 | ||||
msgid "What is the Python Software Foundation?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:35 | ||||
msgid "" | ||||
"The Python Software Foundation is an independent non-profit organization " | ||||
"that holds the copyright on Python versions 2.1 and newer. The PSF's " | ||||
"mission is to advance open source technology related to the Python " | ||||
"programming language and to publicize the use of Python. The PSF's home " | ||||
"page is at https://www.python.org/psf/." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:41 | ||||
msgid "" | ||||
"Donations to the PSF are tax-exempt in the US. If you use Python and find " | ||||
"it helpful, please contribute via `the PSF donation page <https://www.python." | ||||
"org/psf/donations/>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:47 | ||||
msgid "Are there copyright restrictions on the use of Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:49 | ||||
msgid "" | ||||
"You can do anything you want with the source, as long as you leave the " | ||||
"copyrights in and display those copyrights in any documentation about Python " | ||||
"that you produce. If you honor the copyright rules, it's OK to use Python " | ||||
"for commercial use, to sell copies of Python in source or binary form " | ||||
"(modified or unmodified), or to sell products that incorporate Python in " | ||||
"some form. We would still like to know about all commercial use of Python, " | ||||
"of course." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:56 | ||||
msgid "" | ||||
"See `the PSF license page <https://www.python.org/psf/license/>`_ to find " | ||||
"further explanations and a link to the full text of the license." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:59 | ||||
msgid "" | ||||
"The Python logo is trademarked, and in certain cases permission is required " | ||||
"to use it. Consult `the Trademark Usage Policy <https://www.python.org/psf/" | ||||
"trademarks/>`__ for more information." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:65 | ||||
msgid "Why was Python created in the first place?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:67 | ||||
msgid "" | ||||
"Here's a *very* brief summary of what started it all, written by Guido van " | ||||
"Rossum:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:70 | ||||
msgid "" | ||||
"I had extensive experience with implementing an interpreted language in the " | ||||
"ABC group at CWI, and from working with this group I had learned a lot about " | ||||
"language design. This is the origin of many Python features, including the " | ||||
"use of indentation for statement grouping and the inclusion of very-high-" | ||||
"level data types (although the details are all different in Python)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:77 | ||||
msgid "" | ||||
"I had a number of gripes about the ABC language, but also liked many of its " | ||||
"features. It was impossible to extend the ABC language (or its " | ||||
"implementation) to remedy my complaints -- in fact its lack of extensibility " | ||||
"was one of its biggest problems. I had some experience with using Modula-2+ " | ||||
"and talked with the designers of Modula-3 and read the Modula-3 report. " | ||||
"Modula-3 is the origin of the syntax and semantics used for exceptions, and " | ||||
"some other Python features." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:85 | ||||
msgid "" | ||||
"I was working in the Amoeba distributed operating system group at CWI. We " | ||||
"needed a better way to do system administration than by writing either C " | ||||
"programs or Bourne shell scripts, since Amoeba had its own system call " | ||||
"interface which wasn't easily accessible from the Bourne shell. My " | ||||
"experience with error handling in Amoeba made me acutely aware of the " | ||||
"importance of exceptions as a programming language feature." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:92 | ||||
msgid "" | ||||
"It occurred to me that a scripting language with a syntax like ABC but with " | ||||
"access to the Amoeba system calls would fill the need. I realized that it " | ||||
"would be foolish to write an Amoeba-specific language, so I decided that I " | ||||
"needed a language that was generally extensible." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:97 | ||||
msgid "" | ||||
"During the 1989 Christmas holidays, I had a lot of time on my hand, so I " | ||||
"decided to give it a try. During the next year, while still mostly working " | ||||
"on it in my own time, Python was used in the Amoeba project with increasing " | ||||
"success, and the feedback from colleagues made me add many early " | ||||
"improvements." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:103 | ||||
msgid "" | ||||
"In February 1991, after just over a year of development, I decided to post " | ||||
"to USENET. The rest is in the ``Misc/HISTORY`` file." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:108 | ||||
msgid "What is Python good for?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:110 | ||||
msgid "" | ||||
"Python is a high-level general-purpose programming language that can be " | ||||
"applied to many different classes of problems." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:113 | ||||
msgid "" | ||||
"The language comes with a large standard library that covers areas such as " | ||||
"string processing (regular expressions, Unicode, calculating differences " | ||||
"between files), Internet protocols (HTTP, FTP, SMTP, XML-RPC, POP, IMAP, CGI " | ||||
"programming), software engineering (unit testing, logging, profiling, " | ||||
"parsing Python code), and operating system interfaces (system calls, " | ||||
"filesystems, TCP/IP sockets). Look at the table of contents for :ref:" | ||||
"`library-index` to get an idea of what's available. A wide variety of third-" | ||||
"party extensions are also available. Consult `the Python Package Index " | ||||
"<https://pypi.python.org/pypi>`_ to find packages of interest to you." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:125 | ||||
msgid "How does the Python version numbering scheme work?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:127 | ||||
msgid "" | ||||
"Python versions are numbered A.B.C or A.B. A is the major version number -- " | ||||
"it is only incremented for really major changes in the language. B is the " | ||||
"minor version number, incremented for less earth-shattering changes. C is " | ||||
"the micro-level -- it is incremented for each bugfix release. See :pep:`6` " | ||||
"for more information about bugfix releases." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:133 | ||||
msgid "" | ||||
"Not all releases are bugfix releases. In the run-up to a new major release, " | ||||
"a series of development releases are made, denoted as alpha, beta, or " | ||||
"release candidate. Alphas are early releases in which interfaces aren't yet " | ||||
"finalized; it's not unexpected to see an interface change between two alpha " | ||||
"releases. Betas are more stable, preserving existing interfaces but possibly " | ||||
"adding new modules, and release candidates are frozen, making no changes " | ||||
"except as needed to fix critical bugs." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:141 | ||||
msgid "" | ||||
"Alpha, beta and release candidate versions have an additional suffix. The " | ||||
"suffix for an alpha version is \"aN\" for some small number N, the suffix " | ||||
"for a beta version is \"bN\" for some small number N, and the suffix for a " | ||||
"release candidate version is \"cN\" for some small number N. In other " | ||||
"words, all versions labeled 2.0aN precede the versions labeled 2.0bN, which " | ||||
"precede versions labeled 2.0cN, and *those* precede 2.0." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:148 | ||||
msgid "" | ||||
"You may also find version numbers with a \"+\" suffix, e.g. \"2.2+\". These " | ||||
"are unreleased versions, built directly from the CPython development " | ||||
"repository. In practice, after a final minor release is made, the version " | ||||
"is incremented to the next minor version, which becomes the \"a0\" version, " | ||||
"e.g. \"2.4a0\"." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:153 | ||||
msgid "" | ||||
"See also the documentation for :data:`sys.version`, :data:`sys.hexversion`, " | ||||
"and :data:`sys.version_info`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:158 | ||||
msgid "How do I obtain a copy of the Python source?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:160 | ||||
msgid "" | ||||
"The latest Python source distribution is always available from python.org, " | ||||
"at https://www.python.org/downloads/. The latest development sources can be " | ||||
"obtained via anonymous Mercurial access at https://hg.python.org/cpython." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:164 | ||||
msgid "" | ||||
"The source distribution is a gzipped tar file containing the complete C " | ||||
"source, Sphinx-formatted documentation, Python library modules, example " | ||||
"programs, and several useful pieces of freely distributable software. The " | ||||
"source will compile and run out of the box on most UNIX platforms." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:169 | ||||
msgid "" | ||||
"Consult the `Getting Started section of the Python Developer's Guide " | ||||
"<https://docs.python.org/devguide/setup.html>`__ for more information on " | ||||
"getting the source code and compiling it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:175 | ||||
msgid "How do I get documentation on Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:179 | ||||
msgid "" | ||||
"The standard documentation for the current stable version of Python is " | ||||
"available at https://docs.python.org/3/. PDF, plain text, and downloadable " | ||||
"HTML versions are also available at https://docs.python.org/3/download.html." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:183 | ||||
msgid "" | ||||
"The documentation is written in reStructuredText and processed by `the " | ||||
"Sphinx documentation tool <http://sphinx-doc.org/>`__. The reStructuredText " | ||||
"source for the documentation is part of the Python source distribution." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:189 | ||||
msgid "I've never programmed before. Is there a Python tutorial?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:191 | ||||
msgid "" | ||||
"There are numerous tutorials and books available. The standard " | ||||
"documentation includes :ref:`tutorial-index`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:194 | ||||
msgid "" | ||||
"Consult `the Beginner's Guide <https://wiki.python.org/moin/" | ||||
"BeginnersGuide>`_ to find information for beginning Python programmers, " | ||||
"including lists of tutorials." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:199 | ||||
msgid "Is there a newsgroup or mailing list devoted to Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:201 | ||||
msgid "" | ||||
"There is a newsgroup, :newsgroup:`comp.lang.python`, and a mailing list, " | ||||
"`python-list <https://mail.python.org/mailman/listinfo/python-list>`_. The " | ||||
"newsgroup and mailing list are gatewayed into each other -- if you can read " | ||||
"news it's unnecessary to subscribe to the mailing list. :newsgroup:`comp." | ||||
"lang.python` is high-traffic, receiving hundreds of postings every day, and " | ||||
"Usenet readers are often more able to cope with this volume." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:208 | ||||
msgid "" | ||||
"Announcements of new software releases and events can be found in comp.lang." | ||||
"python.announce, a low-traffic moderated list that receives about five " | ||||
"postings per day. It's available as `the python-announce mailing list " | ||||
"<https://mail.python.org/mailman/listinfo/python-announce-list>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:213 | ||||
msgid "" | ||||
"More info about other mailing lists and newsgroups can be found at https://" | ||||
"www.python.org/community/lists/." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:218 | ||||
msgid "How do I get a beta test version of Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:220 | ||||
msgid "" | ||||
"Alpha and beta releases are available from https://www.python.org/" | ||||
"downloads/. All releases are announced on the comp.lang.python and comp." | ||||
"lang.python.announce newsgroups and on the Python home page at https://www." | ||||
"python.org/; an RSS feed of news is available." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:225 | ||||
msgid "" | ||||
"You can also access the development version of Python through Mercurial. " | ||||
"See https://docs.python.org/devguide/faq.html for details." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:230 | ||||
msgid "How do I submit bug reports and patches for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:232 | ||||
msgid "" | ||||
"To report a bug or submit a patch, please use the Roundup installation at " | ||||
"https://bugs.python.org/." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:235 | ||||
msgid "" | ||||
"You must have a Roundup account to report bugs; this makes it possible for " | ||||
"us to contact you if we have follow-up questions. It will also enable " | ||||
"Roundup to send you updates as we act on your bug. If you had previously " | ||||
"used SourceForge to report bugs to Python, you can obtain your Roundup " | ||||
"password through Roundup's `password reset procedure <https://bugs.python." | ||||
"org/user?@template=forgotten>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:241 | ||||
msgid "" | ||||
"For more information on how Python is developed, consult `the Python " | ||||
"Developer's Guide <https://docs.python.org/devguide/>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:246 | ||||
msgid "Are there any published articles about Python that I can reference?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:248 | ||||
msgid "It's probably best to cite your favorite book about Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:250 | ||||
msgid "" | ||||
"The very first article about Python was written in 1991 and is now quite " | ||||
"outdated." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:253 | ||||
msgid "" | ||||
"Guido van Rossum and Jelke de Boer, \"Interactively Testing Remote Servers " | ||||
"Using the Python Programming Language\", CWI Quarterly, Volume 4, Issue 4 " | ||||
"(December 1991), Amsterdam, pp 283-303." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:259 | ||||
msgid "Are there any books on Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:261 | ||||
msgid "" | ||||
"Yes, there are many, and more are being published. See the python.org wiki " | ||||
"at https://wiki.python.org/moin/PythonBooks for a list." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:264 | ||||
msgid "" | ||||
"You can also search online bookstores for \"Python\" and filter out the " | ||||
"Monty Python references; or perhaps search for \"Python\" and \"language\"." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:269 | ||||
msgid "Where in the world is www.python.org located?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:271 | ||||
msgid "" | ||||
"The Python project's infrastructure is located all over the world. `www." | ||||
"python.org <https://www.python.org>`_ is graciously hosted by `Rackspace " | ||||
"<https://www.rackspace.com>`_, with CDN caching provided by `Fastly <https://" | ||||
"www.fastly.com>`_. `Upfront Systems <http://www.upfrontsystems.co.za/>`_ " | ||||
"hosts `bugs.python.org <https://bugs.python.org>`_. Many other Python " | ||||
"services like `the Wiki <https://wiki.python.org>`_ are hosted by `Oregon " | ||||
"State University Open Source Lab <https://osuosl.org>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:282 | ||||
msgid "Why is it called Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:284 | ||||
msgid "" | ||||
"When he began implementing Python, Guido van Rossum was also reading the " | ||||
"published scripts from `\"Monty Python's Flying Circus\" <https://en." | ||||
"wikipedia.org/wiki/Monty_Python>`__, a BBC comedy series from the 1970s. " | ||||
"Van Rossum thought he needed a name that was short, unique, and slightly " | ||||
"mysterious, so he decided to call the language Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:292 | ||||
msgid "Do I have to like \"Monty Python's Flying Circus\"?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:294 | ||||
msgid "No, but it helps. :)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:298 | ||||
msgid "Python in the real world" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:301 | ||||
msgid "How stable is Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:303 | ||||
msgid "" | ||||
"Very stable. New, stable releases have been coming out roughly every 6 to " | ||||
"18 months since 1991, and this seems likely to continue. Currently there " | ||||
"are usually around 18 months between major releases." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:307 | ||||
msgid "" | ||||
"The developers issue \"bugfix\" releases of older versions, so the stability " | ||||
"of existing releases gradually improves. Bugfix releases, indicated by a " | ||||
"third component of the version number (e.g. 2.5.3, 2.6.2), are managed for " | ||||
"stability; only fixes for known problems are included in a bugfix release, " | ||||
"and it's guaranteed that interfaces will remain the same throughout a series " | ||||
"of bugfix releases." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:314 | ||||
msgid "" | ||||
"The latest stable releases can always be found on the `Python download page " | ||||
"<https://www.python.org/downloads/>`_. There are two recommended production-" | ||||
"ready versions at this point in time, because at the moment there are two " | ||||
"branches of stable releases: 2.x and 3.x. Python 3.x may be less useful " | ||||
"than 2.x, since currently there is more third party software available for " | ||||
"Python 2 than for Python 3. Python 2 code will generally not run unchanged " | ||||
"in Python 3." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:323 | ||||
msgid "How many people are using Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:325 | ||||
msgid "" | ||||
"There are probably tens of thousands of users, though it's difficult to " | ||||
"obtain an exact count." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:328 | ||||
msgid "" | ||||
"Python is available for free download, so there are no sales figures, and " | ||||
"it's available from many different sites and packaged with many Linux " | ||||
"distributions, so download statistics don't tell the whole story either." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:332 | ||||
msgid "" | ||||
"The comp.lang.python newsgroup is very active, but not all Python users post " | ||||
"to the group or even read it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:337 | ||||
msgid "Have any significant projects been done in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:339 | ||||
msgid "" | ||||
"See https://www.python.org/about/success for a list of projects that use " | ||||
"Python. Consulting the proceedings for `past Python conferences <https://www." | ||||
"python.org/community/workshops/>`_ will reveal contributions from many " | ||||
"different companies and organizations." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:344 | ||||
msgid "" | ||||
"High-profile Python projects include `the Mailman mailing list manager " | ||||
"<http://www.list.org>`_ and `the Zope application server <http://www.zope." | ||||
"org>`_. Several Linux distributions, most notably `Red Hat <https://www." | ||||
"redhat.com>`_, have written part or all of their installer and system " | ||||
"administration software in Python. Companies that use Python internally " | ||||
"include Google, Yahoo, and Lucasfilm Ltd." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:353 | ||||
msgid "What new developments are expected for Python in the future?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:355 | ||||
msgid "" | ||||
"See https://www.python.org/dev/peps/ for the Python Enhancement Proposals " | ||||
"(PEPs). PEPs are design documents describing a suggested new feature for " | ||||
"Python, providing a concise technical specification and a rationale. Look " | ||||
"for a PEP titled \"Python X.Y Release Schedule\", where X.Y is a version " | ||||
"that hasn't been publicly released yet." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:361 | ||||
msgid "" | ||||
"New development is discussed on `the python-dev mailing list <https://mail." | ||||
"python.org/mailman/listinfo/python-dev/>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:366 | ||||
msgid "Is it reasonable to propose incompatible changes to Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:368 | ||||
msgid "" | ||||
"In general, no. There are already millions of lines of Python code around " | ||||
"the world, so any change in the language that invalidates more than a very " | ||||
"small fraction of existing programs has to be frowned upon. Even if you can " | ||||
"provide a conversion program, there's still the problem of updating all " | ||||
"documentation; many books have been written about Python, and we don't want " | ||||
"to invalidate them all at a single stroke." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:375 | ||||
msgid "" | ||||
"Providing a gradual upgrade path is necessary if a feature has to be " | ||||
"changed. :pep:`5` describes the procedure followed for introducing backward-" | ||||
"incompatible changes while minimizing disruption for users." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:381 | ||||
msgid "Is Python a good language for beginning programmers?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:383 | ||||
msgid "Yes." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:385 | ||||
msgid "" | ||||
"It is still common to start students with a procedural and statically typed " | ||||
"language such as Pascal, C, or a subset of C++ or Java. Students may be " | ||||
"better served by learning Python as their first language. Python has a very " | ||||
"simple and consistent syntax and a large standard library and, most " | ||||
"importantly, using Python in a beginning programming course lets students " | ||||
"concentrate on important programming skills such as problem decomposition " | ||||
"and data type design. With Python, students can be quickly introduced to " | ||||
"basic concepts such as loops and procedures. They can probably even work " | ||||
"with user-defined objects in their very first course." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:395 | ||||
msgid "" | ||||
"For a student who has never programmed before, using a statically typed " | ||||
"language seems unnatural. It presents additional complexity that the " | ||||
"student must master and slows the pace of the course. The students are " | ||||
"trying to learn to think like a computer, decompose problems, design " | ||||
"consistent interfaces, and encapsulate data. While learning to use a " | ||||
"statically typed language is important in the long term, it is not " | ||||
"necessarily the best topic to address in the students' first programming " | ||||
"course." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:403 | ||||
msgid "" | ||||
"Many other aspects of Python make it a good first language. Like Java, " | ||||
"Python has a large standard library so that students can be assigned " | ||||
"programming projects very early in the course that *do* something. " | ||||
"Assignments aren't restricted to the standard four-function calculator and " | ||||
"check balancing programs. By using the standard library, students can gain " | ||||
"the satisfaction of working on realistic applications as they learn the " | ||||
"fundamentals of programming. Using the standard library also teaches " | ||||
"students about code reuse. Third-party modules such as PyGame are also " | ||||
"helpful in extending the students' reach." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:412 | ||||
msgid "" | ||||
"Python's interactive interpreter enables students to test language features " | ||||
"while they're programming. They can keep a window with the interpreter " | ||||
"running while they enter their program's source in another window. If they " | ||||
"can't remember the methods for a list, they can do something like this::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:441 | ||||
msgid "" | ||||
"With the interpreter, documentation is never far from the student as they " | ||||
"are programming." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:444 | ||||
msgid "" | ||||
"There are also good IDEs for Python. IDLE is a cross-platform IDE for " | ||||
"Python that is written in Python using Tkinter. PythonWin is a Windows-" | ||||
"specific IDE. Emacs users will be happy to know that there is a very good " | ||||
"Python mode for Emacs. All of these programming environments provide syntax " | ||||
"highlighting, auto-indenting, and access to the interactive interpreter " | ||||
"while coding. Consult `the Python wiki <https://wiki.python.org/moin/" | ||||
"PythonEditors>`_ for a full list of Python editing environments." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:452 | ||||
msgid "" | ||||
"If you want to discuss Python's use in education, you may be interested in " | ||||
"joining `the edu-sig mailing list <https://www.python.org/community/sigs/" | ||||
"current/edu-sig>`_." | ||||
msgstr "" | ||||
235 faq/gui.po Normal file
235
faq/gui.po Normal file | | @ -0,0 +1,235 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/gui.rst:5 | ||||
msgid "Graphic User Interface FAQ" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:15 | ||||
msgid "General GUI Questions" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:18 | ||||
msgid "What platform-independent GUI toolkits exist for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:20 | ||||
msgid "" | ||||
"Depending on what platform(s) you are aiming at, there are several. Some of " | ||||
"them haven't been ported to Python 3 yet. At least `Tkinter`_ and `Qt`_ are " | ||||
"known to be Python 3-compatible." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:27 | ||||
msgid "Tkinter" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:29 | ||||
msgid "" | ||||
"Standard builds of Python include an object-oriented interface to the Tcl/Tk " | ||||
"widget set, called :ref:`tkinter <Tkinter>`. This is probably the easiest " | ||||
"to install (since it comes included with most `binary distributions <https://" | ||||
"www.python.org/downloads/>`_ of Python) and use. For more info about Tk, " | ||||
"including pointers to the source, see the `Tcl/Tk home page <https://www.tcl." | ||||
"tk>`_. Tcl/Tk is fully portable to the Mac OS X, Windows, and Unix " | ||||
"platforms." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:38 | ||||
msgid "wxWidgets" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:40 | ||||
msgid "" | ||||
"wxWidgets (https://www.wxwidgets.org) is a free, portable GUI class library " | ||||
"written in C++ that provides a native look and feel on a number of " | ||||
"platforms, with Windows, Mac OS X, GTK, X11, all listed as current stable " | ||||
"targets. Language bindings are available for a number of languages " | ||||
"including Python, Perl, Ruby, etc." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:46 | ||||
msgid "" | ||||
"wxPython (http://www.wxpython.org) is the Python binding for wxwidgets. " | ||||
"While it often lags slightly behind the official wxWidgets releases, it also " | ||||
"offers a number of features via pure Python extensions that are not " | ||||
"available in other language bindings. There is an active wxPython user and " | ||||
"developer community." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:52 | ||||
msgid "" | ||||
"Both wxWidgets and wxPython are free, open source, software with permissive " | ||||
"licences that allow their use in commercial products as well as in freeware " | ||||
"or shareware." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:58 | ||||
msgid "Qt" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:60 | ||||
msgid "" | ||||
"There are bindings available for the Qt toolkit (using either `PyQt <https://" | ||||
"riverbankcomputing.com/software/pyqt/intro>`_ or `PySide <https://wiki.qt.io/" | ||||
"PySide>`_) and for KDE (`PyKDE4 <https://techbase.kde.org/Languages/Python/" | ||||
"Using_PyKDE_4>`__). PyQt is currently more mature than PySide, but you must " | ||||
"buy a PyQt license from `Riverbank Computing <https://www.riverbankcomputing." | ||||
"com/commercial/license-faq>`_ if you want to write proprietary " | ||||
"applications. PySide is free for all applications." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:67 | ||||
msgid "" | ||||
"Qt 4.5 upwards is licensed under the LGPL license; also, commercial licenses " | ||||
"are available from `The Qt Company <https://www.qt.io/licensing/>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:71 | ||||
msgid "Gtk+" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:73 | ||||
msgid "" | ||||
"The `GObject introspection bindings <https://wiki.gnome.org/Projects/" | ||||
"PyGObject>`_ for Python allow you to write GTK+ 3 applications. There is " | ||||
"also a `Python GTK+ 3 Tutorial <https://python-gtk-3-tutorial.readthedocs." | ||||
"org/en/latest/>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:77 | ||||
msgid "" | ||||
"The older PyGtk bindings for the `Gtk+ 2 toolkit <http://www.gtk.org>`_ have " | ||||
"been implemented by James Henstridge; see <http://www.pygtk.org>." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:81 | ||||
msgid "FLTK" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:83 | ||||
msgid "" | ||||
"Python bindings for `the FLTK toolkit <http://www.fltk.org>`_, a simple yet " | ||||
"powerful and mature cross-platform windowing system, are available from `the " | ||||
"PyFLTK project <http://pyfltk.sourceforge.net>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:89 | ||||
msgid "FOX" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:91 | ||||
msgid "" | ||||
"A wrapper for `the FOX toolkit <http://www.fox-toolkit.org/>`_ called `FXpy " | ||||
"<http://fxpy.sourceforge.net/>`_ is available. FOX supports both Unix " | ||||
"variants and Windows." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:97 | ||||
msgid "OpenGL" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:99 | ||||
msgid "For OpenGL bindings, see `PyOpenGL <http://pyopengl.sourceforge.net>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:103 | ||||
msgid "What platform-specific GUI toolkits exist for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:105 | ||||
msgid "" | ||||
"By installing the `PyObjc Objective-C bridge <https://pythonhosted.org/" | ||||
"pyobjc/>`_, Python programs can use Mac OS X's Cocoa libraries." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:109 | ||||
msgid "" | ||||
":ref:`Pythonwin <windows-faq>` by Mark Hammond includes an interface to the " | ||||
"Microsoft Foundation Classes and a Python programming environment that's " | ||||
"written mostly in Python using the MFC classes." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:115 | ||||
msgid "Tkinter questions" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:118 | ||||
msgid "How do I freeze Tkinter applications?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:120 | ||||
msgid "" | ||||
"Freeze is a tool to create stand-alone applications. When freezing Tkinter " | ||||
"applications, the applications will not be truly stand-alone, as the " | ||||
"application will still need the Tcl and Tk libraries." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:124 | ||||
msgid "" | ||||
"One solution is to ship the application with the Tcl and Tk libraries, and " | ||||
"point to them at run-time using the :envvar:`TCL_LIBRARY` and :envvar:" | ||||
"`TK_LIBRARY` environment variables." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:128 | ||||
msgid "" | ||||
"To get truly stand-alone applications, the Tcl scripts that form the library " | ||||
"have to be integrated into the application as well. One tool supporting that " | ||||
"is SAM (stand-alone modules), which is part of the Tix distribution (http://" | ||||
"tix.sourceforge.net/)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:133 | ||||
msgid "" | ||||
"Build Tix with SAM enabled, perform the appropriate call to :c:func:" | ||||
"`Tclsam_init`, etc. inside Python's :file:`Modules/tkappinit.c`, and link " | ||||
"with libtclsam and libtksam (you might include the Tix libraries as well)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:140 | ||||
msgid "Can I have Tk events handled while waiting for I/O?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:142 | ||||
msgid "" | ||||
"On platforms other than Windows, yes, and you don't even need threads! But " | ||||
"you'll have to restructure your I/O code a bit. Tk has the equivalent of " | ||||
"Xt's :c:func:`XtAddInput()` call, which allows you to register a callback " | ||||
"function which will be called from the Tk mainloop when I/O is possible on a " | ||||
"file descriptor. See :ref:`tkinter-file-handlers`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:150 | ||||
msgid "I can't get key bindings to work in Tkinter: why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:152 | ||||
msgid "" | ||||
"An often-heard complaint is that event handlers bound to events with the :" | ||||
"meth:`bind` method don't get handled even when the appropriate key is " | ||||
"pressed." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:155 | ||||
msgid "" | ||||
"The most common cause is that the widget to which the binding applies " | ||||
"doesn't have \"keyboard focus\". Check out the Tk documentation for the " | ||||
"focus command. Usually a widget is given the keyboard focus by clicking in " | ||||
"it (but not for labels; see the takefocus option)." | ||||
msgstr "" | ||||
21 faq/index.po Normal file
21
faq/index.po Normal file | | @ -0,0 +1,21 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/index.rst:5 | ||||
msgid "Python Frequently Asked Questions" | ||||
msgstr "" | ||||
108 faq/installed.po Normal file
108
faq/installed.po Normal file | | @ -0,0 +1,108 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/installed.rst:3 | ||||
msgid "\"Why is Python Installed on my Computer?\" FAQ" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:6 | ||||
msgid "What is Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:8 | ||||
msgid "" | ||||
"Python is a programming language. It's used for many different " | ||||
"applications. It's used in some high schools and colleges as an introductory " | ||||
"programming language because Python is easy to learn, but it's also used by " | ||||
"professional software developers at places such as Google, NASA, and " | ||||
"Lucasfilm Ltd." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:13 | ||||
msgid "" | ||||
"If you wish to learn more about Python, start with the `Beginner's Guide to " | ||||
"Python <https://wiki.python.org/moin/BeginnersGuide>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:18 | ||||
msgid "Why is Python installed on my machine?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:20 | ||||
msgid "" | ||||
"If you find Python installed on your system but don't remember installing " | ||||
"it, there are several possible ways it could have gotten there." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:23 | ||||
msgid "" | ||||
"Perhaps another user on the computer wanted to learn programming and " | ||||
"installed it; you'll have to figure out who's been using the machine and " | ||||
"might have installed it." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:26 | ||||
msgid "" | ||||
"A third-party application installed on the machine might have been written " | ||||
"in Python and included a Python installation. There are many such " | ||||
"applications, from GUI programs to network servers and administrative " | ||||
"scripts." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:29 | ||||
msgid "" | ||||
"Some Windows machines also have Python installed. At this writing we're " | ||||
"aware of computers from Hewlett-Packard and Compaq that include Python. " | ||||
"Apparently some of HP/Compaq's administrative tools are written in Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:32 | ||||
msgid "" | ||||
"Many Unix-compatible operating systems, such as Mac OS X and some Linux " | ||||
"distributions, have Python installed by default; it's included in the base " | ||||
"installation." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:38 | ||||
msgid "Can I delete Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:40 | ||||
msgid "That depends on where Python came from." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:42 | ||||
msgid "" | ||||
"If someone installed it deliberately, you can remove it without hurting " | ||||
"anything. On Windows, use the Add/Remove Programs icon in the Control Panel." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:45 | ||||
msgid "" | ||||
"If Python was installed by a third-party application, you can also remove " | ||||
"it, but that application will no longer work. You should use that " | ||||
"application's uninstaller rather than removing Python directly." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/installed.rst:49 | ||||
msgid "" | ||||
"If Python came with your operating system, removing it is not recommended. " | ||||
"If you remove it, whatever tools were written in Python will no longer run, " | ||||
"and some of them might be important to you. Reinstalling the whole system " | ||||
"would then be required to fix things again." | ||||
msgstr "" | ||||
847 faq/library.po Normal file
847
faq/library.po Normal file | | @ -0,0 +1,847 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/library.rst:5 | ||||
msgid "Library and Extension FAQ" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:12 | ||||
msgid "General Library Questions" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:15 | ||||
msgid "How do I find a module or application to perform task X?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:17 | ||||
msgid "" | ||||
"Check :ref:`the Library Reference <library-index>` to see if there's a " | ||||
"relevant standard library module. (Eventually you'll learn what's in the " | ||||
"standard library and will be able to skip this step.)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:21 | ||||
msgid "" | ||||
"For third-party packages, search the `Python Package Index <https://pypi." | ||||
"python.org/pypi>`_ or try `Google <https://www.google.com>`_ or another Web " | ||||
"search engine. Searching for \"Python\" plus a keyword or two for your " | ||||
"topic of interest will usually find something helpful." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:28 | ||||
msgid "Where is the math.py (socket.py, regex.py, etc.) source file?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:30 | ||||
msgid "" | ||||
"If you can't find a source file for a module it may be a built-in or " | ||||
"dynamically loaded module implemented in C, C++ or other compiled language. " | ||||
"In this case you may not have the source file or it may be something like :" | ||||
"file:`mathmodule.c`, somewhere in a C source directory (not on the Python " | ||||
"Path)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:35 | ||||
msgid "There are (at least) three kinds of modules in Python:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:37 | ||||
msgid "modules written in Python (.py);" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:38 | ||||
msgid "" | ||||
"modules written in C and dynamically loaded (.dll, .pyd, .so, .sl, etc);" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:39 | ||||
msgid "" | ||||
"modules written in C and linked with the interpreter; to get a list of " | ||||
"these, type::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:47 | ||||
msgid "How do I make a Python script executable on Unix?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:49 | ||||
msgid "" | ||||
"You need to do two things: the script file's mode must be executable and the " | ||||
"first line must begin with ``#!`` followed by the path of the Python " | ||||
"interpreter." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:53 | ||||
msgid "" | ||||
"The first is done by executing ``chmod +x scriptfile`` or perhaps ``chmod " | ||||
"755 scriptfile``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:56 | ||||
msgid "" | ||||
"The second can be done in a number of ways. The most straightforward way is " | ||||
"to write ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:61 | ||||
msgid "" | ||||
"as the very first line of your file, using the pathname for where the Python " | ||||
"interpreter is installed on your platform." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:64 | ||||
msgid "" | ||||
"If you would like the script to be independent of where the Python " | ||||
"interpreter lives, you can use the :program:`env` program. Almost all Unix " | ||||
"variants support the following, assuming the Python interpreter is in a " | ||||
"directory on the user's :envvar:`PATH`::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:71 | ||||
msgid "" | ||||
"*Don't* do this for CGI scripts. The :envvar:`PATH` variable for CGI " | ||||
"scripts is often very minimal, so you need to use the actual absolute " | ||||
"pathname of the interpreter." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:75 | ||||
msgid "" | ||||
"Occasionally, a user's environment is so full that the :program:`/usr/bin/" | ||||
"env` program fails; or there's no env program at all. In that case, you can " | ||||
"try the following hack (due to Alex Rezinsky)::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:84 | ||||
msgid "" | ||||
"The minor disadvantage is that this defines the script's __doc__ string. " | ||||
"However, you can fix that by adding ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:92 | ||||
msgid "Is there a curses/termcap package for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:96 | ||||
msgid "" | ||||
"For Unix variants: The standard Python source distribution comes with a " | ||||
"curses module in the :source:`Modules` subdirectory, though it's not " | ||||
"compiled by default. (Note that this is not available in the Windows " | ||||
"distribution -- there is no curses module for Windows.)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:101 | ||||
msgid "" | ||||
"The :mod:`curses` module supports basic curses features as well as many " | ||||
"additional functions from ncurses and SYSV curses such as colour, " | ||||
"alternative character set support, pads, and mouse support. This means the " | ||||
"module isn't compatible with operating systems that only have BSD curses, " | ||||
"but there don't seem to be any currently maintained OSes that fall into this " | ||||
"category." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:107 | ||||
msgid "" | ||||
"For Windows: use `the consolelib module <http://effbot.org/zone/console-" | ||||
"index.htm>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:112 | ||||
msgid "Is there an equivalent to C's onexit() in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:114 | ||||
msgid "" | ||||
"The :mod:`atexit` module provides a register function that is similar to " | ||||
"C's :c:func:`onexit`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:119 | ||||
msgid "Why don't my signal handlers work?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:121 | ||||
msgid "" | ||||
"The most common problem is that the signal handler is declared with the " | ||||
"wrong argument list. It is called as ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:126 | ||||
msgid "so it should be declared with two arguments::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:133 | ||||
msgid "Common tasks" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:136 | ||||
msgid "How do I test a Python program or component?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:138 | ||||
msgid "" | ||||
"Python comes with two testing frameworks. The :mod:`doctest` module finds " | ||||
"examples in the docstrings for a module and runs them, comparing the output " | ||||
"with the expected output given in the docstring." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:142 | ||||
msgid "" | ||||
"The :mod:`unittest` module is a fancier testing framework modelled on Java " | ||||
"and Smalltalk testing frameworks." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:145 | ||||
msgid "" | ||||
"To make testing easier, you should use good modular design in your program. " | ||||
"Your program should have almost all functionality encapsulated in either " | ||||
"functions or class methods -- and this sometimes has the surprising and " | ||||
"delightful effect of making the program run faster (because local variable " | ||||
"accesses are faster than global accesses). Furthermore the program should " | ||||
"avoid depending on mutating global variables, since this makes testing much " | ||||
"more difficult to do." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:153 | ||||
msgid "The \"global main logic\" of your program may be as simple as ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:158 | ||||
msgid "at the bottom of the main module of your program." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:160 | ||||
msgid "" | ||||
"Once your program is organized as a tractable collection of functions and " | ||||
"class behaviours you should write test functions that exercise the " | ||||
"behaviours. A test suite that automates a sequence of tests can be " | ||||
"associated with each module. This sounds like a lot of work, but since " | ||||
"Python is so terse and flexible it's surprisingly easy. You can make coding " | ||||
"much more pleasant and fun by writing your test functions in parallel with " | ||||
"the \"production code\", since this makes it easy to find bugs and even " | ||||
"design flaws earlier." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:168 | ||||
msgid "" | ||||
"\"Support modules\" that are not intended to be the main module of a program " | ||||
"may include a self-test of the module. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:174 | ||||
msgid "" | ||||
"Even programs that interact with complex external interfaces may be tested " | ||||
"when the external interfaces are unavailable by using \"fake\" interfaces " | ||||
"implemented in Python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:180 | ||||
msgid "How do I create documentation from doc strings?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:182 | ||||
msgid "" | ||||
"The :mod:`pydoc` module can create HTML from the doc strings in your Python " | ||||
"source code. An alternative for creating API documentation purely from " | ||||
"docstrings is `epydoc <http://epydoc.sourceforge.net/>`_. `Sphinx <http://" | ||||
"sphinx-doc.org>`_ can also include docstring content." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:189 | ||||
msgid "How do I get a single keypress at a time?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:191 | ||||
msgid "" | ||||
"For Unix variants there are several solutions. It's straightforward to do " | ||||
"this using curses, but curses is a fairly large module to learn." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:235 | ||||
msgid "Threads" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:238 | ||||
msgid "How do I program using threads?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:240 | ||||
msgid "" | ||||
"Be sure to use the :mod:`threading` module and not the :mod:`_thread` " | ||||
"module. The :mod:`threading` module builds convenient abstractions on top of " | ||||
"the low-level primitives provided by the :mod:`_thread` module." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:244 | ||||
msgid "" | ||||
"Aahz has a set of slides from his threading tutorial that are helpful; see " | ||||
"http://www.pythoncraft.com/OSCON2001/." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:249 | ||||
msgid "None of my threads seem to run: why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:251 | ||||
msgid "" | ||||
"As soon as the main thread exits, all threads are killed. Your main thread " | ||||
"is running too quickly, giving the threads no time to do any work." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:254 | ||||
msgid "" | ||||
"A simple fix is to add a sleep to the end of the program that's long enough " | ||||
"for all the threads to finish::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:269 | ||||
msgid "" | ||||
"But now (on many platforms) the threads don't run in parallel, but appear to " | ||||
"run sequentially, one at a time! The reason is that the OS thread scheduler " | ||||
"doesn't start a new thread until the previous thread is blocked." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:273 | ||||
msgid "A simple fix is to add a tiny sleep to the start of the run function::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:286 | ||||
msgid "" | ||||
"Instead of trying to guess a good delay value for :func:`time.sleep`, it's " | ||||
"better to use some kind of semaphore mechanism. One idea is to use the :mod:" | ||||
"`queue` module to create a queue object, let each thread append a token to " | ||||
"the queue when it finishes, and let the main thread read as many tokens from " | ||||
"the queue as there are threads." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:294 | ||||
msgid "How do I parcel out work among a bunch of worker threads?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:296 | ||||
msgid "" | ||||
"The easiest way is to use the new :mod:`concurrent.futures` module, " | ||||
"especially the :mod:`~concurrent.futures.ThreadPoolExecutor` class." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:299 | ||||
msgid "" | ||||
"Or, if you want fine control over the dispatching algorithm, you can write " | ||||
"your own logic manually. Use the :mod:`queue` module to create a queue " | ||||
"containing a list of jobs. The :class:`~queue.Queue` class maintains a list " | ||||
"of objects and has a ``.put(obj)`` method that adds items to the queue and a " | ||||
"``.get()`` method to return them. The class will take care of the locking " | ||||
"necessary to ensure that each job is handed out exactly once." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:306 | ||||
msgid "Here's a trivial example::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:344 | ||||
msgid "When run, this will produce the following output:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:362 | ||||
msgid "" | ||||
"Consult the module's documentation for more details; the :class:`~queue." | ||||
"Queue` class provides a featureful interface." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:367 | ||||
msgid "What kinds of global value mutation are thread-safe?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:369 | ||||
msgid "" | ||||
"A :term:`global interpreter lock` (GIL) is used internally to ensure that " | ||||
"only one thread runs in the Python VM at a time. In general, Python offers " | ||||
"to switch among threads only between bytecode instructions; how frequently " | ||||
"it switches can be set via :func:`sys.setswitchinterval`. Each bytecode " | ||||
"instruction and therefore all the C implementation code reached from each " | ||||
"instruction is therefore atomic from the point of view of a Python program." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:376 | ||||
msgid "" | ||||
"In theory, this means an exact accounting requires an exact understanding of " | ||||
"the PVM bytecode implementation. In practice, it means that operations on " | ||||
"shared variables of built-in data types (ints, lists, dicts, etc) that " | ||||
"\"look atomic\" really are." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:381 | ||||
msgid "" | ||||
"For example, the following operations are all atomic (L, L1, L2 are lists, " | ||||
"D, D1, D2 are dicts, x, y are objects, i, j are ints)::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:396 | ||||
msgid "These aren't::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:403 | ||||
msgid "" | ||||
"Operations that replace other objects may invoke those other objects' :meth:" | ||||
"`__del__` method when their reference count reaches zero, and that can " | ||||
"affect things. This is especially true for the mass updates to dictionaries " | ||||
"and lists. When in doubt, use a mutex!" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:410 | ||||
msgid "Can't we get rid of the Global Interpreter Lock?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:414 | ||||
msgid "" | ||||
"The :term:`global interpreter lock` (GIL) is often seen as a hindrance to " | ||||
"Python's deployment on high-end multiprocessor server machines, because a " | ||||
"multi-threaded Python program effectively only uses one CPU, due to the " | ||||
"insistence that (almost) all Python code can only run while the GIL is held." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:419 | ||||
msgid "" | ||||
"Back in the days of Python 1.5, Greg Stein actually implemented a " | ||||
"comprehensive patch set (the \"free threading\" patches) that removed the " | ||||
"GIL and replaced it with fine-grained locking. Adam Olsen recently did a " | ||||
"similar experiment in his `python-safethread <http://code.google.com/p/" | ||||
"python-safethread/>`_ project. Unfortunately, both experiments exhibited a " | ||||
"sharp drop in single-thread performance (at least 30% slower), due to the " | ||||
"amount of fine-grained locking necessary to compensate for the removal of " | ||||
"the GIL." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:427 | ||||
msgid "" | ||||
"This doesn't mean that you can't make good use of Python on multi-CPU " | ||||
"machines! You just have to be creative with dividing the work up between " | ||||
"multiple *processes* rather than multiple *threads*. The :class:" | ||||
"`~concurrent.futures.ProcessPoolExecutor` class in the new :mod:`concurrent." | ||||
"futures` module provides an easy way of doing so; the :mod:`multiprocessing` " | ||||
"module provides a lower-level API in case you want more control over " | ||||
"dispatching of tasks." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:435 | ||||
msgid "" | ||||
"Judicious use of C extensions will also help; if you use a C extension to " | ||||
"perform a time-consuming task, the extension can release the GIL while the " | ||||
"thread of execution is in the C code and allow other threads to get some " | ||||
"work done. Some standard library modules such as :mod:`zlib` and :mod:" | ||||
"`hashlib` already do this." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:441 | ||||
msgid "" | ||||
"It has been suggested that the GIL should be a per-interpreter-state lock " | ||||
"rather than truly global; interpreters then wouldn't be able to share " | ||||
"objects. Unfortunately, this isn't likely to happen either. It would be a " | ||||
"tremendous amount of work, because many object implementations currently " | ||||
"have global state. For example, small integers and short strings are cached; " | ||||
"these caches would have to be moved to the interpreter state. Other object " | ||||
"types have their own free list; these free lists would have to be moved to " | ||||
"the interpreter state. And so on." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:450 | ||||
msgid "" | ||||
"And I doubt that it can even be done in finite time, because the same " | ||||
"problem exists for 3rd party extensions. It is likely that 3rd party " | ||||
"extensions are being written at a faster rate than you can convert them to " | ||||
"store all their global state in the interpreter state." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:455 | ||||
msgid "" | ||||
"And finally, once you have multiple interpreters not sharing any state, what " | ||||
"have you gained over running each interpreter in a separate process?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:460 | ||||
msgid "Input and Output" | ||||
msgstr "Les entrées/sorties" | ||||
| ||||
#: ../Doc/faq/library.rst:463 | ||||
msgid "How do I delete a file? (And other file questions...)" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:465 | ||||
msgid "" | ||||
"Use ``os.remove(filename)`` or ``os.unlink(filename)``; for documentation, " | ||||
"see the :mod:`os` module. The two functions are identical; :func:`~os." | ||||
"unlink` is simply the name of the Unix system call for this function." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:469 | ||||
msgid "" | ||||
"To remove a directory, use :func:`os.rmdir`; use :func:`os.mkdir` to create " | ||||
"one. ``os.makedirs(path)`` will create any intermediate directories in " | ||||
"``path`` that don't exist. ``os.removedirs(path)`` will remove intermediate " | ||||
"directories as long as they're empty; if you want to delete an entire " | ||||
"directory tree and its contents, use :func:`shutil.rmtree`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:475 | ||||
msgid "To rename a file, use ``os.rename(old_path, new_path)``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:477 | ||||
msgid "" | ||||
"To truncate a file, open it using ``f = open(filename, \"rb+\")``, and use " | ||||
"``f.truncate(offset)``; offset defaults to the current seek position. " | ||||
"There's also ``os.ftruncate(fd, offset)`` for files opened with :func:`os." | ||||
"open`, where *fd* is the file descriptor (a small integer)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:482 | ||||
msgid "" | ||||
"The :mod:`shutil` module also contains a number of functions to work on " | ||||
"files including :func:`~shutil.copyfile`, :func:`~shutil.copytree`, and :" | ||||
"func:`~shutil.rmtree`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:488 | ||||
msgid "How do I copy a file?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:490 | ||||
msgid "" | ||||
"The :mod:`shutil` module contains a :func:`~shutil.copyfile` function. Note " | ||||
"that on MacOS 9 it doesn't copy the resource fork and Finder info." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:495 | ||||
msgid "How do I read (or write) binary data?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:497 | ||||
msgid "" | ||||
"To read or write complex binary data formats, it's best to use the :mod:" | ||||
"`struct` module. It allows you to take a string containing binary data " | ||||
"(usually numbers) and convert it to Python objects; and vice versa." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:501 | ||||
msgid "" | ||||
"For example, the following code reads two 2-byte integers and one 4-byte " | ||||
"integer in big-endian format from a file::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:510 | ||||
msgid "" | ||||
"The '>' in the format string forces big-endian data; the letter 'h' reads " | ||||
"one \"short integer\" (2 bytes), and 'l' reads one \"long integer\" (4 " | ||||
"bytes) from the string." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:514 | ||||
msgid "" | ||||
"For data that is more regular (e.g. a homogeneous list of ints or floats), " | ||||
"you can also use the :mod:`array` module." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:519 | ||||
msgid "" | ||||
"To read and write binary data, it is mandatory to open the file in binary " | ||||
"mode (here, passing ``\"rb\"`` to :func:`open`). If you use ``\"r\"`` " | ||||
"instead (the default), the file will be open in text mode and ``f.read()`` " | ||||
"will return :class:`str` objects rather than :class:`bytes` objects." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:527 | ||||
msgid "I can't seem to use os.read() on a pipe created with os.popen(); why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:529 | ||||
msgid "" | ||||
":func:`os.read` is a low-level function which takes a file descriptor, a " | ||||
"small integer representing the opened file. :func:`os.popen` creates a high-" | ||||
"level file object, the same type returned by the built-in :func:`open` " | ||||
"function. Thus, to read *n* bytes from a pipe *p* created with :func:`os." | ||||
"popen`, you need to use ``p.read(n)``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:616 | ||||
msgid "How do I access the serial (RS232) port?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:618 | ||||
msgid "For Win32, POSIX (Linux, BSD, etc.), Jython:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:620 | ||||
msgid "http://pyserial.sourceforge.net" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:622 | ||||
msgid "For Unix, see a Usenet post by Mitch Chapman:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:624 | ||||
msgid "https://groups.google.com/groups?selm=34A04430.CF9@ohioee.com" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:628 | ||||
msgid "Why doesn't closing sys.stdout (stdin, stderr) really close it?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:630 | ||||
msgid "" | ||||
"Python :term:`file objects <file object>` are a high-level layer of " | ||||
"abstraction on low-level C file descriptors." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:633 | ||||
msgid "" | ||||
"For most file objects you create in Python via the built-in :func:`open` " | ||||
"function, ``f.close()`` marks the Python file object as being closed from " | ||||
"Python's point of view, and also arranges to close the underlying C file " | ||||
"descriptor. This also happens automatically in ``f``'s destructor, when " | ||||
"``f`` becomes garbage." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:639 | ||||
msgid "" | ||||
"But stdin, stdout and stderr are treated specially by Python, because of the " | ||||
"special status also given to them by C. Running ``sys.stdout.close()`` " | ||||
"marks the Python-level file object as being closed, but does *not* close the " | ||||
"associated C file descriptor." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:644 | ||||
msgid "" | ||||
"To close the underlying C file descriptor for one of these three, you should " | ||||
"first be sure that's what you really want to do (e.g., you may confuse " | ||||
"extension modules trying to do I/O). If it is, use :func:`os.close`::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:652 | ||||
msgid "Or you can use the numeric constants 0, 1 and 2, respectively." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:656 | ||||
msgid "Network/Internet Programming" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:659 | ||||
msgid "What WWW tools are there for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:661 | ||||
msgid "" | ||||
"See the chapters titled :ref:`internet` and :ref:`netdata` in the Library " | ||||
"Reference Manual. Python has many modules that will help you build server-" | ||||
"side and client-side web systems." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:667 | ||||
msgid "" | ||||
"A summary of available frameworks is maintained by Paul Boddie at https://" | ||||
"wiki.python.org/moin/WebProgramming\\ ." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:670 | ||||
msgid "" | ||||
"Cameron Laird maintains a useful set of pages about Python web technologies " | ||||
"at http://phaseit.net/claird/comp.lang.python/web_python." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:675 | ||||
msgid "How can I mimic CGI form submission (METHOD=POST)?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:677 | ||||
msgid "" | ||||
"I would like to retrieve web pages that are the result of POSTing a form. Is " | ||||
"there existing code that would let me do this easily?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:680 | ||||
msgid "Yes. Here's a simple example that uses urllib.request::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:695 | ||||
msgid "" | ||||
"Note that in general for percent-encoded POST operations, query strings must " | ||||
"be quoted using :func:`urllib.parse.urlencode`. For example, to send " | ||||
"``name=Guy Steele, Jr.``::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:703 | ||||
msgid ":ref:`urllib-howto` for extensive examples." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:707 | ||||
msgid "What module should I use to help with generating HTML?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:711 | ||||
msgid "" | ||||
"You can find a collection of useful links on the `Web Programming wiki page " | ||||
"<https://wiki.python.org/moin/WebProgramming>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:716 | ||||
msgid "How do I send mail from a Python script?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:718 | ||||
msgid "Use the standard library module :mod:`smtplib`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:720 | ||||
msgid "" | ||||
"Here's a very simple interactive mail sender that uses it. This method will " | ||||
"work on any host that supports an SMTP listener. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:740 | ||||
msgid "" | ||||
"A Unix-only alternative uses sendmail. The location of the sendmail program " | ||||
"varies between systems; sometimes it is ``/usr/lib/sendmail``, sometimes ``/" | ||||
"usr/sbin/sendmail``. The sendmail manual page will help you out. Here's " | ||||
"some sample code::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:760 | ||||
msgid "How do I avoid blocking in the connect() method of a socket?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:762 | ||||
msgid "" | ||||
"The :mod:`select` module is commonly used to help with asynchronous I/O on " | ||||
"sockets." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:765 | ||||
msgid "" | ||||
"To prevent the TCP connect from blocking, you can set the socket to non-" | ||||
"blocking mode. Then when you do the ``connect()``, you will either connect " | ||||
"immediately (unlikely) or get an exception that contains the error number as " | ||||
"``.errno``. ``errno.EINPROGRESS`` indicates that the connection is in " | ||||
"progress, but hasn't finished yet. Different OSes will return different " | ||||
"values, so you're going to have to check what's returned on your system." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:772 | ||||
msgid "" | ||||
"You can use the ``connect_ex()`` method to avoid creating an exception. It " | ||||
"will just return the errno value. To poll, you can call ``connect_ex()`` " | ||||
"again later -- ``0`` or ``errno.EISCONN`` indicate that you're connected -- " | ||||
"or you can pass this socket to select to check if it's writable." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:778 | ||||
msgid "" | ||||
"The :mod:`asyncore` module presents a framework-like approach to the problem " | ||||
"of writing non-blocking networking code. The third-party `Twisted <https://" | ||||
"twistedmatrix.com/trac/>`_ library is a popular and feature-rich alternative." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:785 | ||||
msgid "Databases" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:788 | ||||
msgid "Are there any interfaces to database packages in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:790 | ||||
msgid "Yes." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:792 | ||||
msgid "" | ||||
"Interfaces to disk-based hashes such as :mod:`DBM <dbm.ndbm>` and :mod:`GDBM " | ||||
"<dbm.gnu>` are also included with standard Python. There is also the :mod:" | ||||
"`sqlite3` module, which provides a lightweight disk-based relational " | ||||
"database." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:797 | ||||
msgid "" | ||||
"Support for most relational databases is available. See the " | ||||
"`DatabaseProgramming wiki page <https://wiki.python.org/moin/" | ||||
"DatabaseProgramming>`_ for details." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:803 | ||||
msgid "How do you implement persistent objects in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:805 | ||||
msgid "" | ||||
"The :mod:`pickle` library module solves this in a very general way (though " | ||||
"you still can't store things like open files, sockets or windows), and the :" | ||||
"mod:`shelve` library module uses pickle and (g)dbm to create persistent " | ||||
"mappings containing arbitrary Python objects." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:812 | ||||
msgid "Mathematics and Numerics" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:815 | ||||
msgid "How do I generate random numbers in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:817 | ||||
msgid "" | ||||
"The standard module :mod:`random` implements a random number generator. " | ||||
"Usage is simple::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:823 | ||||
msgid "This returns a random floating point number in the range [0, 1)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:825 | ||||
msgid "" | ||||
"There are also many other specialized generators in this module, such as:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:827 | ||||
msgid "``randrange(a, b)`` chooses an integer in the range [a, b)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:828 | ||||
msgid "``uniform(a, b)`` chooses a floating point number in the range [a, b)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:829 | ||||
msgid "" | ||||
"``normalvariate(mean, sdev)`` samples the normal (Gaussian) distribution." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:831 | ||||
msgid "Some higher-level functions operate on sequences directly, such as:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:833 | ||||
msgid "``choice(S)`` chooses random element from a given sequence" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:834 | ||||
msgid "``shuffle(L)`` shuffles a list in-place, i.e. permutes it randomly" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/library.rst:836 | ||||
msgid "" | ||||
"There's also a ``Random`` class you can instantiate to create independent " | ||||
"multiple random number generators." | ||||
msgstr "" | ||||
2437 faq/programming.po Normal file
2437
faq/programming.po Normal file File diff suppressed because it is too large Load diff
448 faq/windows.po Normal file
448
faq/windows.po Normal file | | @ -0,0 +1,448 @@ | |||
# SOME DESCRIPTIVE TITLE. | ||||
# Copyright (C) 2001-2016, Python Software Foundation | ||||
# This file is distributed under the same license as the Python package. | ||||
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. | ||||
# | ||||
#, fuzzy | ||||
msgid "" | ||||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\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" | ||||
| ||||
#: ../Doc/faq/windows.rst:7 | ||||
msgid "Python on Windows FAQ" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:18 | ||||
msgid "How do I run a Python program under Windows?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:20 | ||||
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:0 | ||||
msgid "|Python Development on XP|_" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:27 | ||||
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:36 | ||||
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:46 | ||||
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:51 | ||||
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:55 | ||||
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:60 | ||||
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:67 | ||||
msgid "You should then see something like::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:73 | ||||
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:83 | ||||
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:88 | ||||
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:94 | ||||
msgid "" | ||||
"If the ``python`` command, instead of displaying the interpreter prompt " | ||||
"``>>>``, gives you a message like::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:0 | ||||
msgid "|Adding Python to DOS Path|_" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:102 | ||||
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:111 | ||||
msgid "or::" | ||||
msgstr "ou : ::" | ||||
| ||||
#: ../Doc/faq/windows.rst:115 | ||||
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:119 | ||||
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:125 | ||||
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:134 | ||||
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:140 | ||||
msgid "" | ||||
"More information about environment variables can be found on the :ref:`Using " | ||||
"Python on Windows <setting-envvars>` page." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:144 | ||||
msgid "How do I make Python scripts executable?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:146 | ||||
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:154 | ||||
msgid "Why does Python sometimes take so long to start?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:156 | ||||
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:161 | ||||
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:171 | ||||
msgid "How do I make an executable from a Python script?" | ||||
msgstr "Comment construire un exécutable depuis un script Python ?" | ||||
| ||||
#: ../Doc/faq/windows.rst:173 | ||||
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:181 | ||||
msgid "Is a ``*.pyd`` file the same as a DLL?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:183 | ||||
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:190 | ||||
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:199 | ||||
msgid "How can I embed Python into a Windows application?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:201 | ||||
msgid "" | ||||
"Embedding the Python interpreter in a Windows app can be summarized as " | ||||
"follows:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:203 | ||||
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:209 | ||||
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:215 | ||||
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:222 | ||||
msgid "" | ||||
"Borland note: convert :file:`python{NN}.lib` to OMF format using Coff2Omf." | ||||
"exe first." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:227 | ||||
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:233 | ||||
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:239 | ||||
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:243 | ||||
msgid "" | ||||
"In short, you can use the following code to initialize the Python " | ||||
"interpreter with your extension module." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:254 | ||||
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:257 | ||||
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:262 | ||||
msgid "" | ||||
"Problem 2: SWIG generates the following code when generating wrappers to " | ||||
"void functions:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:271 | ||||
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:279 | ||||
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:283 | ||||
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:292 | ||||
msgid "How do I keep editors from inserting tabs into my Python source?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:294 | ||||
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:298 | ||||
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:303 | ||||
msgid "" | ||||
"If you suspect mixed tabs and spaces are causing problems in leading " | ||||
"whitespace, run Python with the :option:`-t` switch or run ``Tools/Scripts/" | ||||
"tabnanny.py`` to check a directory tree in batch mode." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:309 | ||||
msgid "How do I check for a keypress without blocking?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:311 | ||||
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:317 | ||||
msgid "How do I emulate os.kill() in Windows?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:319 | ||||
msgid "" | ||||
"Prior to Python 2.7 and 3.2, to terminate a process, you can use :mod:" | ||||
"`ctypes`::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:329 | ||||
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:335 | ||||
msgid "How do I extract the downloaded documentation on Windows?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:337 | ||||
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:341 | ||||
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 "" | ||||
Loading…
Add table
Add a link
Reference in a new issue