3.6: merge pot files
This commit is contained in:
parent d1a5d291b1
commit a25cddd031
463 changed files with 31928 additions and 26519 deletions
257 faq/design.po
257
faq/design.po | | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | @ -74,11 +75,12 @@ msgstr "" | |||
"autre style." | ||||
| ||||
#: ../Doc/faq/design.rst:31 | ||||
#, fuzzy | ||||
msgid "" | ||||
"Many coding styles place begin/end brackets on a line by themselves. This " | ||||
"makes programs considerably longer and wastes valuable screen space, making " | ||||
"it harder to get a good overview of a program. Ideally, a function should " | ||||
"fit on one screen (say, 20-30 lines). 20 lines of Python can do a lot more " | ||||
"fit on one screen (say, 20--30 lines). 20 lines of Python can do a lot more " | ||||
"work than 20 lines of C. This is not solely due to the lack of begin/end " | ||||
"brackets -- the lack of declarations and the high-level data types are also " | ||||
"responsible -- but the indentation-based syntax certainly helps." | ||||
| | @ -164,8 +166,9 @@ msgid "which is exactly::" | |||
msgstr "qui est, exactement : ::" | ||||
| ||||
#: ../Doc/faq/design.rst:80 | ||||
#, fuzzy | ||||
msgid "" | ||||
"The typical precision of 53 bits provides Python floats with 15-16 decimal " | ||||
"The typical precision of 53 bits provides Python floats with 15--16 decimal " | ||||
"digits of accuracy." | ||||
msgstr "" | ||||
"La précision typique, de 53 bits, permet une précision de 15-16 décimales " | ||||
| | @ -680,64 +683,19 @@ msgstr "" | |||
"Python peut-il être compilé en code machine, en C ou dans un autre langage ?" | ||||
| ||||
#: ../Doc/faq/design.rst:369 | ||||
msgid "Practical answer:" | ||||
msgstr "Réponse concrète :" | ||||
| ||||
#: ../Doc/faq/design.rst:371 | ||||
msgid "" | ||||
"`Cython <http://cython.org/>`_ and `Pyrex <https://www.cosc.canterbury.ac.nz/" | ||||
"greg.ewing/python/Pyrex/>`_ compile a modified version of Python with " | ||||
"optional annotations into C extensions. `Weave <https://scipy.github.io/" | ||||
"devdocs/tutorial/weave.html>`_ makes it easy to intermingle Python and C " | ||||
"code in various ways to increase performance. `Nuitka <http://www.nuitka.net/" | ||||
">`_ is an up-and-coming compiler of Python into C++ code, aiming to support " | ||||
"the full Python language." | ||||
"`Cython <http://cython.org/>`_ compiles a modified version of Python with " | ||||
"optional annotations into C extensions. `Nuitka <http://www.nuitka.net/>`_ " | ||||
"is an up-and-coming compiler of Python into C++ code, aiming to support the " | ||||
"full Python language. For compiling to Java you can consider `VOC <https://" | ||||
"voc.readthedocs.io>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:378 | ||||
msgid "Theoretical answer:" | ||||
msgstr "Réponse théorique :" | ||||
| ||||
#: ../Doc/faq/design.rst:382 | ||||
msgid "" | ||||
"Not trivially. Python's high level data types, dynamic typing of objects " | ||||
"and run-time invocation of the interpreter (using :func:`eval` or :func:" | ||||
"`exec`) together mean that a naïvely \"compiled\" Python program would " | ||||
"probably consist mostly of calls into the Python run-time system, even for " | ||||
"seemingly simple operations like ``x+1``." | ||||
msgstr "" | ||||
"Pas de façon triviale. Les types de données haut niveau de Python, le typage " | ||||
"dynamique des objets et l'invocation de l’interpréteur à l'exécution (via :" | ||||
"func:`eval` ou :func:`exec`) font qu'un programme Python compilé naïvement " | ||||
"consisterait probablement principalement à faire des appels au système " | ||||
"d'exécution de Python, même pour des opérations simples comme ``x + 1``." | ||||
| ||||
#: ../Doc/faq/design.rst:388 | ||||
msgid "" | ||||
"Several projects described in the Python newsgroup or at past `Python " | ||||
"conferences <https://www.python.org/community/workshops/>`_ have shown that " | ||||
"this approach is feasible, although the speedups reached so far are only " | ||||
"modest (e.g. 2x). Jython uses the same strategy for compiling to Java " | ||||
"bytecode. (Jim Hugunin has demonstrated that in combination with whole-" | ||||
"program analysis, speedups of 1000x are feasible for small demo programs. " | ||||
"See the proceedings from the `1997 Python conference <http://legacy.python." | ||||
"org/workshops/1997-10/proceedings/>`_ for more information.)" | ||||
msgstr "" | ||||
"Plusieurs projets décrits dans le forum de Python ou dans les anciennes " | ||||
"`Conférences Python <https://www.python.org/community/workshops/>`_ ont " | ||||
"montré que cette approche est réalisable, même si les améliorations " | ||||
"atteintes restaient modestes (autour de ×2). Jython utilise la même " | ||||
"stratégie pour compiler en *bytecode* Java. (Jim Hugunin a démontré qu'en " | ||||
"combinaison avec une analyse de la totalité du programme, des améliorations " | ||||
"de ×1000 sont possibles sur de petits programmes de démonstration. Voir le " | ||||
"compte rendu de la `Conférence de Python 1997 <http://legacy.python.org/" | ||||
"workshops/1997-10/proceedings/>`_ pour plus d'informations.)" | ||||
| ||||
#: ../Doc/faq/design.rst:399 | ||||
#: ../Doc/faq/design.rst:377 | ||||
msgid "How does Python manage memory?" | ||||
msgstr "Comment Python gère la mémoire ?" | ||||
| ||||
#: ../Doc/faq/design.rst:401 | ||||
#: ../Doc/faq/design.rst:379 | ||||
msgid "" | ||||
"The details of Python memory management depend on the implementation. The " | ||||
"standard implementation of Python, :term:`CPython`, uses reference counting " | ||||
| | @ -756,7 +714,7 @@ msgstr "" | |||
"module :mod:`gc` fournit des fonctions pour lancer le ramasse-miettes, " | ||||
"d'obtenir des statistiques de débogage et ajuster ses paramètres." | ||||
| ||||
#: ../Doc/faq/design.rst:409 | ||||
#: ../Doc/faq/design.rst:387 | ||||
msgid "" | ||||
"Other implementations (such as `Jython <http://www.jython.org>`_ or `PyPy " | ||||
"<http://www.pypy.org>`_), however, can rely on a different mechanism such as " | ||||
| | @ -770,7 +728,7 @@ msgstr "" | |||
"subtils problèmes de portabilité si votre code Python dépend du comportement " | ||||
"de l'implémentation du compteur de références." | ||||
| ||||
#: ../Doc/faq/design.rst:415 | ||||
#: ../Doc/faq/design.rst:393 | ||||
msgid "" | ||||
"In some Python implementations, the following code (which is fine in " | ||||
"CPython) will probably run out of file descriptors::" | ||||
| | @ -779,7 +737,7 @@ msgstr "" | |||
"parfaitement avec *CPython*) aurait probablement manqué de descripteurs de " | ||||
"fichiers::" | ||||
| ||||
#: ../Doc/faq/design.rst:422 | ||||
#: ../Doc/faq/design.rst:400 | ||||
msgid "" | ||||
"Indeed, using CPython's reference counting and destructor scheme, each new " | ||||
"assignment to *f* closes the previous file. With a traditional GC, however, " | ||||
| | @ -792,7 +750,7 @@ msgstr "" | |||
"(et fermés) à intervalles variables et possiblement avec de longs " | ||||
"intervalles." | ||||
| ||||
#: ../Doc/faq/design.rst:427 | ||||
#: ../Doc/faq/design.rst:405 | ||||
msgid "" | ||||
"If you want to write code that will work with any Python implementation, you " | ||||
"should explicitly close the file or use the :keyword:`with` statement; this " | ||||
| | @ -803,12 +761,12 @@ msgstr "" | |||
"utiliser l'instruction :keyword:`with` ; ceci fonctionnera indépendamment du " | ||||
"système de gestion de la mémoire::" | ||||
| ||||
#: ../Doc/faq/design.rst:437 | ||||
#: ../Doc/faq/design.rst:415 | ||||
msgid "Why doesn't CPython use a more traditional garbage collection scheme?" | ||||
msgstr "" | ||||
"Pourquoi CPython n'utilise-il pas un ramasse-miette plus traditionnel ?" | ||||
| ||||
#: ../Doc/faq/design.rst:439 | ||||
#: ../Doc/faq/design.rst:417 | ||||
msgid "" | ||||
"For one thing, this is not a C standard feature and hence it's not portable. " | ||||
"(Yes, we know about the Boehm GC library. It has bits of assembler code for " | ||||
| | @ -823,7 +781,7 @@ msgstr "" | |||
"transparent, c'est loin d'être le cas, des correctifs sont nécessaires afin " | ||||
"que Python fonctionne correctement avec.)" | ||||
| ||||
#: ../Doc/faq/design.rst:445 | ||||
#: ../Doc/faq/design.rst:423 | ||||
msgid "" | ||||
"Traditional GC also becomes a problem when Python is embedded into other " | ||||
"applications. While in a standalone Python it's fine to replace the " | ||||
| | @ -840,12 +798,12 @@ msgstr "" | |||
"pas vouloir celles de Python. À l'heure actuelle, CPython fonctionne avec " | ||||
"n'importe quelle implémentation correcte de malloc() et free()." | ||||
| ||||
#: ../Doc/faq/design.rst:454 | ||||
#: ../Doc/faq/design.rst:432 | ||||
msgid "Why isn't all memory freed when CPython exits?" | ||||
msgstr "" | ||||
"Pourquoi toute la mémoire n'est pas libérée lorsque *CPython* s'arrête ?" | ||||
| ||||
#: ../Doc/faq/design.rst:456 | ||||
#: ../Doc/faq/design.rst:434 | ||||
msgid "" | ||||
"Objects referenced from the global namespaces of Python modules are not " | ||||
"always deallocated when Python exits. This may happen if there are circular " | ||||
| | @ -862,7 +820,7 @@ msgstr "" | |||
"cependant, agressif sur le nettoyage de la mémoire en quittant et cherche à " | ||||
"détruire chaque objet." | ||||
| ||||
#: ../Doc/faq/design.rst:463 | ||||
#: ../Doc/faq/design.rst:441 | ||||
msgid "" | ||||
"If you want to force Python to delete certain things on deallocation use " | ||||
"the :mod:`atexit` module to run a function that will force those deletions." | ||||
| | @ -871,12 +829,12 @@ msgstr "" | |||
"utilisez le module :mod:`texit` pour exécuter une fonction qui va forcer ces " | ||||
"destructions." | ||||
| ||||
#: ../Doc/faq/design.rst:468 | ||||
#: ../Doc/faq/design.rst:446 | ||||
msgid "Why are there separate tuple and list data types?" | ||||
msgstr "" | ||||
"Pourquoi les *tuples* et les *list* sont deux types de données séparés ?" | ||||
| ||||
#: ../Doc/faq/design.rst:470 | ||||
#: ../Doc/faq/design.rst:448 | ||||
msgid "" | ||||
"Lists and tuples, while similar in many respects, are generally used in " | ||||
"fundamentally different ways. Tuples can be thought of as being similar to " | ||||
| | @ -893,7 +851,7 @@ msgstr "" | |||
"un repère cartésien est correctement représenté comme un *tuple* de deux ou " | ||||
"trois nombres." | ||||
| ||||
#: ../Doc/faq/design.rst:477 | ||||
#: ../Doc/faq/design.rst:455 | ||||
msgid "" | ||||
"Lists, on the other hand, are more like arrays in other languages. They " | ||||
"tend to hold a varying number of objects all of which have the same type and " | ||||
| | @ -910,7 +868,7 @@ msgstr "" | |||
"problème que vous ajoutiez un ou deux fichiers supplémentaire dans le " | ||||
"dossier." | ||||
| ||||
#: ../Doc/faq/design.rst:484 | ||||
#: ../Doc/faq/design.rst:462 | ||||
msgid "" | ||||
"Tuples are immutable, meaning that once a tuple has been created, you can't " | ||||
"replace any of its elements with a new value. Lists are mutable, meaning " | ||||
| | @ -925,11 +883,11 @@ msgstr "" | |||
"utilisés comme clés de dictionnaires, et donc de ``tuple`` et ``list`` seul " | ||||
"des *tuples* peuvent être utilisés comme clés." | ||||
| ||||
#: ../Doc/faq/design.rst:491 | ||||
#: ../Doc/faq/design.rst:469 | ||||
msgid "How are lists implemented?" | ||||
msgstr "Comment est-ce que les listes sont implémentées ?" | ||||
| ||||
#: ../Doc/faq/design.rst:493 | ||||
#: ../Doc/faq/design.rst:471 | ||||
msgid "" | ||||
"Python's lists are really variable-length arrays, not Lisp-style linked " | ||||
"lists. The implementation uses a contiguous array of references to other " | ||||
| | @ -942,7 +900,7 @@ msgstr "" | |||
"Elle conserve également un pointeur vers ce tableau et la longueur du " | ||||
"tableau dans une structure de tête de liste." | ||||
| ||||
#: ../Doc/faq/design.rst:497 | ||||
#: ../Doc/faq/design.rst:475 | ||||
msgid "" | ||||
"This makes indexing a list ``a[i]`` an operation whose cost is independent " | ||||
"of the size of the list or the value of the index." | ||||
| | @ -950,7 +908,7 @@ msgstr "" | |||
"Cela rend l'indexation d'une liste ``a[i]`` une opération dont le coût est " | ||||
"indépendant de la taille de la liste ou de la valeur de l'indice." | ||||
| ||||
#: ../Doc/faq/design.rst:500 | ||||
#: ../Doc/faq/design.rst:478 | ||||
msgid "" | ||||
"When items are appended or inserted, the array of references is resized. " | ||||
"Some cleverness is applied to improve the performance of appending items " | ||||
| | @ -963,11 +921,11 @@ msgstr "" | |||
"être étendu, un certain espace supplémentaire est alloué de sorte que pour " | ||||
"la prochaine fois, ceci ne nécessite plus un redimensionnement effectif." | ||||
| ||||
#: ../Doc/faq/design.rst:507 | ||||
#: ../Doc/faq/design.rst:485 | ||||
msgid "How are dictionaries implemented?" | ||||
msgstr "Comment les dictionnaires sont-ils implémentés ?" | ||||
| ||||
#: ../Doc/faq/design.rst:509 | ||||
#: ../Doc/faq/design.rst:487 | ||||
msgid "" | ||||
"Python's dictionaries are implemented as resizable hash tables. Compared to " | ||||
"B-trees, this gives better performance for lookup (the most common operation " | ||||
| | @ -978,7 +936,7 @@ msgstr "" | |||
"performances pour la recherche (l'opération la plus courante de loin) dans " | ||||
"la plupart des circonstances, et leur implémentation est plus simple." | ||||
| ||||
#: ../Doc/faq/design.rst:513 | ||||
#: ../Doc/faq/design.rst:491 | ||||
msgid "" | ||||
"Dictionaries work by computing a hash code for each key stored in the " | ||||
"dictionary using the :func:`hash` built-in function. The hash code varies " | ||||
| | @ -1010,11 +968,11 @@ msgstr "" | |||
"du dictionnaire dans un certain ordre arbitraire qui peut changer à chaque " | ||||
"appel d'un programme." | ||||
| ||||
#: ../Doc/faq/design.rst:528 | ||||
#: ../Doc/faq/design.rst:506 | ||||
msgid "Why must dictionary keys be immutable?" | ||||
msgstr "Pourquoi les clés du dictionnaire sont immuables ?" | ||||
| ||||
#: ../Doc/faq/design.rst:530 | ||||
#: ../Doc/faq/design.rst:508 | ||||
msgid "" | ||||
"The hash table implementation of dictionaries uses a hash value calculated " | ||||
"from the key value to find the key. If the key were a mutable object, its " | ||||
| | @ -1037,7 +995,7 @@ msgstr "" | |||
"chercher l'ancienne valeur, elle serait également introuvable car la valeur " | ||||
"de l'objet trouvé dans cet emplacement de hachage serait différente." | ||||
| ||||
#: ../Doc/faq/design.rst:539 | ||||
#: ../Doc/faq/design.rst:517 | ||||
msgid "" | ||||
"If you want a dictionary indexed with a list, simply convert the list to a " | ||||
"tuple first; the function ``tuple(L)`` creates a tuple with the same entries " | ||||
| | @ -1049,11 +1007,11 @@ msgstr "" | |||
"*tuple* avec les mêmes entrées que la liste ``L``. Les *tuples* sont " | ||||
"immuables et peuvent donc être utilisés comme clés du dictionnaire." | ||||
| ||||
#: ../Doc/faq/design.rst:543 | ||||
#: ../Doc/faq/design.rst:521 | ||||
msgid "Some unacceptable solutions that have been proposed:" | ||||
msgstr "Certaines solutions insatisfaisantes qui ont été proposées :" | ||||
| ||||
#: ../Doc/faq/design.rst:545 | ||||
#: ../Doc/faq/design.rst:523 | ||||
msgid "" | ||||
"Hash lists by their address (object ID). This doesn't work because if you " | ||||
"construct a new list with the same value it won't be found; e.g.::" | ||||
| | @ -1062,7 +1020,7 @@ msgstr "" | |||
"fonctionne pas parce que si vous créez une nouvelle liste avec la même " | ||||
"valeur, elle ne sera pas retrouvée; par exemple.::" | ||||
| ||||
#: ../Doc/faq/design.rst:551 | ||||
#: ../Doc/faq/design.rst:529 | ||||
msgid "" | ||||
"would raise a KeyError exception because the id of the ``[1, 2]`` used in " | ||||
"the second line differs from that in the first line. In other words, " | ||||
| | @ -1073,7 +1031,7 @@ msgstr "" | |||
"d'autres termes, les clés de dictionnaire doivent être comparées à l'aide du " | ||||
"comparateur ``==`` et non à l'aide du :keyword:`is`." | ||||
| ||||
#: ../Doc/faq/design.rst:555 | ||||
#: ../Doc/faq/design.rst:533 | ||||
msgid "" | ||||
"Make a copy when using a list as a key. This doesn't work because the list, " | ||||
"being a mutable object, could contain a reference to itself, and then the " | ||||
| | @ -1084,7 +1042,7 @@ msgstr "" | |||
"une référence à elle-même ou avoir une boucle infinie au niveau du code " | ||||
"copié." | ||||
| ||||
#: ../Doc/faq/design.rst:559 | ||||
#: ../Doc/faq/design.rst:537 | ||||
msgid "" | ||||
"Allow lists as keys but tell the user not to modify them. This would allow " | ||||
"a class of hard-to-track bugs in programs when you forgot or modified a list " | ||||
| | @ -1092,7 +1050,7 @@ msgid "" | |||
"every value in ``d.keys()`` is usable as a key of the dictionary." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:564 | ||||
#: ../Doc/faq/design.rst:542 | ||||
msgid "" | ||||
"Mark lists as read-only once they are used as a dictionary key. The problem " | ||||
"is that it's not just the top-level object that could change its value; you " | ||||
| | @ -1102,7 +1060,7 @@ msgid "" | |||
"loop." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:570 | ||||
#: ../Doc/faq/design.rst:548 | ||||
msgid "" | ||||
"There is a trick to get around this if you need to, but use it at your own " | ||||
"risk: You can wrap a mutable structure inside a class instance which has " | ||||
| | @ -1112,14 +1070,14 @@ msgid "" | |||
"in the dictionary (or other structure). ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:594 | ||||
#: ../Doc/faq/design.rst:572 | ||||
msgid "" | ||||
"Note that the hash computation is complicated by the possibility that some " | ||||
"members of the list may be unhashable and also by the possibility of " | ||||
"arithmetic overflow." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:598 | ||||
#: ../Doc/faq/design.rst:576 | ||||
msgid "" | ||||
"Furthermore it must always be the case that if ``o1 == o2`` (ie ``o1." | ||||
"__eq__(o2) is True``) then ``hash(o1) == hash(o2)`` (ie, ``o1.__hash__() == " | ||||
| | @ -1128,7 +1086,7 @@ msgid "" | |||
"based structures will misbehave." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:603 | ||||
#: ../Doc/faq/design.rst:581 | ||||
msgid "" | ||||
"In the case of ListWrapper, whenever the wrapper object is in a dictionary " | ||||
"the wrapped list must not change to avoid anomalies. Don't do this unless " | ||||
| | @ -1136,11 +1094,11 @@ msgid "" | |||
"of not meeting them correctly. Consider yourself warned." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:610 | ||||
#: ../Doc/faq/design.rst:588 | ||||
msgid "Why doesn't list.sort() return the sorted list?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:612 | ||||
#: ../Doc/faq/design.rst:590 | ||||
msgid "" | ||||
"In situations where performance matters, making a copy of the list just to " | ||||
"sort it would be wasteful. Therefore, :meth:`list.sort` sorts the list in " | ||||
| | @ -1150,7 +1108,7 @@ msgid "" | |||
"around." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:618 | ||||
#: ../Doc/faq/design.rst:596 | ||||
msgid "" | ||||
"If you want to return a new list, use the built-in :func:`sorted` function " | ||||
"instead. This function creates a new list from a provided iterable, sorts " | ||||
| | @ -1158,11 +1116,11 @@ msgid "" | |||
"dictionary in sorted order::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:628 | ||||
#: ../Doc/faq/design.rst:606 | ||||
msgid "How do you specify and enforce an interface spec in Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:630 | ||||
#: ../Doc/faq/design.rst:608 | ||||
msgid "" | ||||
"An interface specification for a module as provided by languages such as C++ " | ||||
"and Java describes the prototypes for the methods and functions of the " | ||||
| | @ -1170,7 +1128,7 @@ msgid "" | |||
"helps in the construction of large programs." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:635 | ||||
#: ../Doc/faq/design.rst:613 | ||||
msgid "" | ||||
"Python 2.6 adds an :mod:`abc` module that lets you define Abstract Base " | ||||
"Classes (ABCs). You can then use :func:`isinstance` and :func:`issubclass` " | ||||
| | @ -1180,14 +1138,14 @@ msgid "" | |||
"`~collections.abc.MutableMapping`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:642 | ||||
#: ../Doc/faq/design.rst:620 | ||||
msgid "" | ||||
"For Python, many of the advantages of interface specifications can be " | ||||
"obtained by an appropriate test discipline for components. There is also a " | ||||
"tool, PyChecker, which can be used to find problems due to subclassing." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:646 | ||||
#: ../Doc/faq/design.rst:624 | ||||
msgid "" | ||||
"A good test suite for a module can both provide a regression test and serve " | ||||
"as a module interface specification and a set of examples. Many Python " | ||||
| | @ -1199,7 +1157,7 @@ msgid "" | |||
"in a module." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:654 | ||||
#: ../Doc/faq/design.rst:632 | ||||
msgid "" | ||||
"An appropriate testing discipline can help build large complex applications " | ||||
"in Python as well as having interface specifications would. In fact, it can " | ||||
| | @ -1210,7 +1168,7 @@ msgid "" | |||
"correctly, but it's trivial to check this property in a test suite." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:662 | ||||
#: ../Doc/faq/design.rst:640 | ||||
msgid "" | ||||
"Writing test suites is very helpful, and you might want to design your code " | ||||
"with an eye to making it easily tested. One increasingly popular technique, " | ||||
| | @ -1219,11 +1177,11 @@ msgid "" | |||
"sloppy and not write test cases at all." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:670 | ||||
#: ../Doc/faq/design.rst:648 | ||||
msgid "Why is there no goto?" | ||||
msgstr "Pourquoi n'y a-t-il pas de goto en Python ?" | ||||
| ||||
#: ../Doc/faq/design.rst:672 | ||||
#: ../Doc/faq/design.rst:650 | ||||
msgid "" | ||||
"You can use exceptions to provide a \"structured goto\" that even works " | ||||
"across function calls. Many feel that exceptions can conveniently emulate " | ||||
| | @ -1236,7 +1194,7 @@ msgstr "" | |||
"utilisation raisonnable des constructions \"go\" ou \"goto\" en C, en " | ||||
"Fortran ou autres langages de programmation. Par exemple::" | ||||
| ||||
#: ../Doc/faq/design.rst:687 | ||||
#: ../Doc/faq/design.rst:665 | ||||
msgid "" | ||||
"This doesn't allow you to jump into the middle of a loop, but that's usually " | ||||
"considered an abuse of goto anyway. Use sparingly." | ||||
| | @ -1245,18 +1203,18 @@ msgstr "" | |||
"tous les cas cela est généralement considéré comme un abus de goto. À " | ||||
"Utiliser avec parcimonie." | ||||
| ||||
#: ../Doc/faq/design.rst:692 | ||||
#: ../Doc/faq/design.rst:670 | ||||
msgid "Why can't raw strings (r-strings) end with a backslash?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:694 | ||||
#: ../Doc/faq/design.rst:672 | ||||
msgid "" | ||||
"More precisely, they can't end with an odd number of backslashes: the " | ||||
"unpaired backslash at the end escapes the closing quote character, leaving " | ||||
"an unterminated string." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:698 | ||||
#: ../Doc/faq/design.rst:676 | ||||
msgid "" | ||||
"Raw strings were designed to ease creating input for processors (chiefly " | ||||
"regular expression engines) that want to do their own backslash escape " | ||||
| | @ -1266,24 +1224,24 @@ msgid "" | |||
"rules work well when r-strings are used for their intended purpose." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:705 | ||||
#: ../Doc/faq/design.rst:683 | ||||
msgid "" | ||||
"If you're trying to build Windows pathnames, note that all Windows system " | ||||
"calls accept forward slashes too::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:710 | ||||
#: ../Doc/faq/design.rst:688 | ||||
msgid "" | ||||
"If you're trying to build a pathname for a DOS command, try e.g. one of ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:718 | ||||
#: ../Doc/faq/design.rst:696 | ||||
msgid "Why doesn't Python have a \"with\" statement for attribute assignments?" | ||||
msgstr "" | ||||
"Pourquoi la déclaration \"with\" pour les assignations d'attributs n'existe " | ||||
"pas en Python ?" | ||||
| ||||
#: ../Doc/faq/design.rst:720 | ||||
#: ../Doc/faq/design.rst:698 | ||||
msgid "" | ||||
"Python has a 'with' statement that wraps the execution of a block, calling " | ||||
"code on the entrance and exit from the block. Some language have a " | ||||
| | @ -1293,11 +1251,11 @@ msgstr "" | |||
"appelant le code sur l'entrée et la sortie du bloc. Certains langages " | ||||
"possèdent une construction qui ressemble à ceci::" | ||||
| ||||
#: ../Doc/faq/design.rst:728 | ||||
#: ../Doc/faq/design.rst:706 | ||||
msgid "In Python, such a construct would be ambiguous." | ||||
msgstr "En Python, une telle construction serait ambiguë." | ||||
| ||||
#: ../Doc/faq/design.rst:730 | ||||
#: ../Doc/faq/design.rst:708 | ||||
msgid "" | ||||
"Other languages, such as Object Pascal, Delphi, and C++, use static types, " | ||||
"so it's possible to know, in an unambiguous way, what member is being " | ||||
| | @ -1310,7 +1268,7 @@ msgstr "" | |||
"statique --le compilateur connaît *toujours* la portée de toutes les " | ||||
"variables au moment de la compilation." | ||||
| ||||
#: ../Doc/faq/design.rst:735 | ||||
#: ../Doc/faq/design.rst:713 | ||||
msgid "" | ||||
"Python uses dynamic types. It is impossible to know in advance which " | ||||
"attribute will be referenced at runtime. Member attributes may be added or " | ||||
| | @ -1324,11 +1282,11 @@ msgstr "" | |||
"impossible de savoir, d'une simple lecture, quel attribut est référencé : " | ||||
"s'il est local, global ou un attribut membre?" | ||||
| ||||
#: ../Doc/faq/design.rst:741 | ||||
#: ../Doc/faq/design.rst:719 | ||||
msgid "For instance, take the following incomplete snippet::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:747 | ||||
#: ../Doc/faq/design.rst:725 | ||||
msgid "" | ||||
"The snippet assumes that \"a\" must have a member attribute called \"x\". " | ||||
"However, there is nothing in Python that tells the interpreter this. What " | ||||
| | @ -1337,46 +1295,46 @@ msgid "" | |||
"the dynamic nature of Python makes such choices much harder." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:753 | ||||
#: ../Doc/faq/design.rst:731 | ||||
msgid "" | ||||
"The primary benefit of \"with\" and similar language features (reduction of " | ||||
"code volume) can, however, easily be achieved in Python by assignment. " | ||||
"Instead of::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:760 | ||||
#: ../Doc/faq/design.rst:738 | ||||
msgid "write this::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:767 | ||||
#: ../Doc/faq/design.rst:745 | ||||
msgid "" | ||||
"This also has the side-effect of increasing execution speed because name " | ||||
"bindings are resolved at run-time in Python, and the second version only " | ||||
"needs to perform the resolution once." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:773 | ||||
#: ../Doc/faq/design.rst:751 | ||||
msgid "Why are colons required for the if/while/def/class statements?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:775 | ||||
#: ../Doc/faq/design.rst:753 | ||||
msgid "" | ||||
"The colon is required primarily to enhance readability (one of the results " | ||||
"of the experimental ABC language). Consider this::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:781 | ||||
#: ../Doc/faq/design.rst:759 | ||||
msgid "versus ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:786 | ||||
#: ../Doc/faq/design.rst:764 | ||||
msgid "" | ||||
"Notice how the second one is slightly easier to read. Notice further how a " | ||||
"colon sets off the example in this FAQ answer; it's a standard usage in " | ||||
"English." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:789 | ||||
#: ../Doc/faq/design.rst:767 | ||||
msgid "" | ||||
"Another minor reason is that the colon makes it easier for editors with " | ||||
"syntax highlighting; they can look for colons to decide when indentation " | ||||
| | @ -1384,21 +1342,21 @@ msgid "" | |||
"the program text." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:795 | ||||
#: ../Doc/faq/design.rst:773 | ||||
msgid "Why does Python allow commas at the end of lists and tuples?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:797 | ||||
#: ../Doc/faq/design.rst:775 | ||||
msgid "" | ||||
"Python lets you add a trailing comma at the end of lists, tuples, and " | ||||
"dictionaries::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:808 | ||||
#: ../Doc/faq/design.rst:786 | ||||
msgid "There are several reasons to allow this." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:810 | ||||
#: ../Doc/faq/design.rst:788 | ||||
msgid "" | ||||
"When you have a literal value for a list, tuple, or dictionary spread across " | ||||
"multiple lines, it's easier to add more elements because you don't have to " | ||||
| | @ -1406,21 +1364,62 @@ msgid "" | |||
"reordered without creating a syntax error." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:815 | ||||
#: ../Doc/faq/design.rst:793 | ||||
msgid "" | ||||
"Accidentally omitting the comma can lead to errors that are hard to " | ||||
"diagnose. For example::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:825 | ||||
#: ../Doc/faq/design.rst:803 | ||||
msgid "" | ||||
"This list looks like it has four elements, but it actually contains three: " | ||||
"\"fee\", \"fiefoo\" and \"fum\". Always adding the comma avoids this source " | ||||
"of error." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/design.rst:828 | ||||
#: ../Doc/faq/design.rst:806 | ||||
msgid "" | ||||
"Allowing the trailing comma may also make programmatic code generation " | ||||
"easier." | ||||
msgstr "" | ||||
| ||||
#~ msgid "Practical answer:" | ||||
#~ msgstr "Réponse concrète :" | ||||
| ||||
#~ msgid "Theoretical answer:" | ||||
#~ msgstr "Réponse théorique :" | ||||
| ||||
#~ msgid "" | ||||
#~ "Not trivially. Python's high level data types, dynamic typing of objects " | ||||
#~ "and run-time invocation of the interpreter (using :func:`eval` or :func:" | ||||
#~ "`exec`) together mean that a naïvely \"compiled\" Python program would " | ||||
#~ "probably consist mostly of calls into the Python run-time system, even " | ||||
#~ "for seemingly simple operations like ``x+1``." | ||||
#~ msgstr "" | ||||
#~ "Pas de façon triviale. Les types de données haut niveau de Python, le " | ||||
#~ "typage dynamique des objets et l'invocation de l’interpréteur à " | ||||
#~ "l'exécution (via :func:`eval` ou :func:`exec`) font qu'un programme " | ||||
#~ "Python compilé naïvement consisterait probablement principalement à faire " | ||||
#~ "des appels au système d'exécution de Python, même pour des opérations " | ||||
#~ "simples comme ``x + 1``." | ||||
| ||||
#~ msgid "" | ||||
#~ "Several projects described in the Python newsgroup or at past `Python " | ||||
#~ "conferences <https://www.python.org/community/workshops/>`_ have shown " | ||||
#~ "that this approach is feasible, although the speedups reached so far are " | ||||
#~ "only modest (e.g. 2x). Jython uses the same strategy for compiling to " | ||||
#~ "Java bytecode. (Jim Hugunin has demonstrated that in combination with " | ||||
#~ "whole-program analysis, speedups of 1000x are feasible for small demo " | ||||
#~ "programs. See the proceedings from the `1997 Python conference <http://" | ||||
#~ "legacy.python.org/workshops/1997-10/proceedings/>`_ for more information.)" | ||||
#~ msgstr "" | ||||
#~ "Plusieurs projets décrits dans le forum de Python ou dans les anciennes " | ||||
#~ "`Conférences Python <https://www.python.org/community/workshops/>`_ ont " | ||||
#~ "montré que cette approche est réalisable, même si les améliorations " | ||||
#~ "atteintes restaient modestes (autour de ×2). Jython utilise la même " | ||||
#~ "stratégie pour compiler en *bytecode* Java. (Jim Hugunin a démontré qu'en " | ||||
#~ "combinaison avec une analyse de la totalité du programme, des " | ||||
#~ "améliorations de ×1000 sont possibles sur de petits programmes de " | ||||
#~ "démonstration. Voir le compte rendu de la `Conférence de Python 1997 " | ||||
#~ "<http://legacy.python.org/workshops/1997-10/proceedings/>`_ pour plus " | ||||
#~ "d'informations.)" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | @ -240,7 +241,7 @@ msgstr "" | |||
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." | ||||
"obtained at https://github.com/python/cpython/." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:164 | ||||
| | @ -335,8 +336,8 @@ 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." | ||||
"You can also access the development version of Python through Git. See `The " | ||||
"Python Developer's Guide <https://docs.python.org/devguide/>`_ for details." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:230 | ||||
| | @ -383,7 +384,7 @@ msgstr "" | |||
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." | ||||
"(December 1991), Amsterdam, pp 283--303." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/general.rst:259 | ||||
| | | |||
58 faq/gui.po
58
faq/gui.po | | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | @ -122,75 +123,92 @@ msgid "" | |||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:81 | ||||
msgid "FLTK" | ||||
msgid "Kivy" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:83 | ||||
msgid "" | ||||
"`Kivy <https://kivy.org/>`_ is a cross-platform GUI library supporting both " | ||||
"desktop operating systems (Windows, macOS, Linux) and mobile devices " | ||||
"(Android, iOS). It is written in Python and Cython, and can use a range of " | ||||
"windowing backends." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:88 | ||||
msgid "" | ||||
"Kivy is free and open source software distributed under the MIT license." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:91 | ||||
msgid "FLTK" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:93 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:99 | ||||
msgid "FOX" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:91 | ||||
#: ../Doc/faq/gui.rst:101 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:107 | ||||
msgid "OpenGL" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:99 | ||||
#: ../Doc/faq/gui.rst:109 | ||||
msgid "For OpenGL bindings, see `PyOpenGL <http://pyopengl.sourceforge.net>`_." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:103 | ||||
#: ../Doc/faq/gui.rst:113 | ||||
msgid "What platform-specific GUI toolkits exist for Python?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:105 | ||||
#: ../Doc/faq/gui.rst:115 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:119 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:125 | ||||
msgid "Tkinter questions" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:118 | ||||
#: ../Doc/faq/gui.rst:128 | ||||
msgid "How do I freeze Tkinter applications?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:120 | ||||
#: ../Doc/faq/gui.rst:130 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:134 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:138 | ||||
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 " | ||||
| | @ -198,18 +216,18 @@ msgid "" | |||
"tix.sourceforge.net/)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:133 | ||||
#: ../Doc/faq/gui.rst:143 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:150 | ||||
msgid "Can I have Tk events handled while waiting for I/O?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:142 | ||||
#: ../Doc/faq/gui.rst:152 | ||||
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 " | ||||
| | @ -218,18 +236,18 @@ msgid "" | |||
"file descriptor. See :ref:`tkinter-file-handlers`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:150 | ||||
#: ../Doc/faq/gui.rst:160 | ||||
msgid "I can't get key bindings to work in Tkinter: why?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/gui.rst:152 | ||||
#: ../Doc/faq/gui.rst:162 | ||||
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 | ||||
#: ../Doc/faq/gui.rst:165 | ||||
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 " | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | | |||
| | @ -8,10 +8,11 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2016-10-30 10:40+0100\n" | ||||
"POT-Creation-Date: 2017-04-02 22:11+0200\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" | ||||
"Language: \n" | ||||
"MIME-Version: 1.0\n" | ||||
"Content-Type: text/plain; charset=UTF-8\n" | ||||
"Content-Transfer-Encoding: 8bit\n" | ||||
| | @ -395,33 +396,33 @@ 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." | ||||
"Python raises :exc:`IndentationError` or :exc:`TabError` if mixed tabs and " | ||||
"spaces are causing problems in leading whitespace. You may also run the :mod:" | ||||
"`tabnanny` module to check a directory tree in batch mode." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:309 | ||||
#: ../Doc/faq/windows.rst:310 | ||||
msgid "How do I check for a keypress without blocking?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:311 | ||||
#: ../Doc/faq/windows.rst:312 | ||||
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 | ||||
#: ../Doc/faq/windows.rst:318 | ||||
msgid "How do I emulate os.kill() in Windows?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:319 | ||||
#: ../Doc/faq/windows.rst:320 | ||||
msgid "" | ||||
"Prior to Python 2.7 and 3.2, to terminate a process, you can use :mod:" | ||||
"`ctypes`::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:329 | ||||
#: ../Doc/faq/windows.rst:330 | ||||
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` " | ||||
| | @ -429,18 +430,18 @@ msgid "" | |||
"those signals. See :func:`os.kill` for further details." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:335 | ||||
#: ../Doc/faq/windows.rst:336 | ||||
msgid "How do I extract the downloaded documentation on Windows?" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/faq/windows.rst:337 | ||||
#: ../Doc/faq/windows.rst:338 | ||||
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 | ||||
#: ../Doc/faq/windows.rst:342 | ||||
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 " | ||||
| | | |||
Loading…
Add table
Add a link
Reference in a new issue