GitHub parent a6f49d9513
commit 7b88307273
53 changed files with 2943 additions and 864 deletions
| | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2020-10-01 16:00+0200\n" | ||||
"POT-Creation-Date: 2021-03-19 16:59+0100\n" | ||||
"PO-Revision-Date: 2020-11-07 16:24+0100\n" | ||||
"Last-Translator: Mindiell <mindiell@mindiell.net>\n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -1198,7 +1198,18 @@ msgstr "Pourquoi n'y a-t-il pas de ``goto`` en Python ?" | |||
| ||||
#: faq/design.rst:604 | ||||
msgid "" | ||||
"You can use exceptions to provide a \"structured goto\" that even works " | ||||
"In the 1970s people realized that unrestricted goto could lead to messy " | ||||
"\"spaghetti\" code that was hard to understand and revise. In a high-level " | ||||
"language, it is also unneeded as long as there are ways to branch (in " | ||||
"Python, with ``if`` statements and ``or``, ``and``, and ``if-else`` " | ||||
"expressions) and loop (with ``while`` and ``for`` statements, possibly " | ||||
"containing ``continue`` and ``break``)." | ||||
msgstr "" | ||||
| ||||
#: faq/design.rst:611 | ||||
#, fuzzy | ||||
msgid "" | ||||
"One can also use exceptions to provide a \"structured goto\" that works even " | ||||
"across function calls. Many feel that exceptions can conveniently emulate " | ||||
"all reasonable uses of the \"go\" or \"goto\" constructs of C, Fortran, and " | ||||
"other languages. For example::" | ||||
| | @ -1209,7 +1220,7 @@ msgstr "" | |||
"utilisation raisonnable des constructions ``go`` ou ``goto`` en C, en " | ||||
"Fortran ou autres langages de programmation. Par exemple ::" | ||||
| ||||
#: faq/design.rst:619 | ||||
#: faq/design.rst:627 | ||||
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." | ||||
| | @ -1218,13 +1229,13 @@ msgstr "" | |||
"tous les cas cela est généralement considéré comme un abus de ``goto``. À " | ||||
"Utiliser avec parcimonie." | ||||
| ||||
#: faq/design.rst:624 | ||||
#: faq/design.rst:632 | ||||
msgid "Why can't raw strings (r-strings) end with a backslash?" | ||||
msgstr "" | ||||
"Pourquoi les chaînes de caractères brutes (r-strings) ne peuvent-elles pas " | ||||
"se terminer par un *backslash* ?" | ||||
| ||||
#: faq/design.rst:626 | ||||
#: faq/design.rst:634 | ||||
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 " | ||||
| | @ -1234,7 +1245,7 @@ msgstr "" | |||
"*backslashes* : le *backslash* non appairé à la fin échappe le caractère de " | ||||
"guillemet final, laissant une chaîne non terminée." | ||||
| ||||
#: faq/design.rst:630 | ||||
#: faq/design.rst:638 | ||||
msgid "" | ||||
"Raw strings were designed to ease creating input for processors (chiefly " | ||||
"regular expression engines) that want to do their own backslash escape " | ||||
| | @ -1252,7 +1263,7 @@ msgstr "" | |||
"chaîne en l'échappant avec un *antislash*. Ces règles fonctionnent bien " | ||||
"lorsque les chaînes brutes sont utilisées pour leur but premier." | ||||
| ||||
#: faq/design.rst:637 | ||||
#: faq/design.rst:645 | ||||
msgid "" | ||||
"If you're trying to build Windows pathnames, note that all Windows system " | ||||
"calls accept forward slashes too::" | ||||
| | @ -1261,20 +1272,20 @@ msgstr "" | |||
"les appels système Windows acceptent également les *slashes* \"classiques" | ||||
"\" ::" | ||||
| ||||
#: faq/design.rst:642 | ||||
#: faq/design.rst:650 | ||||
msgid "" | ||||
"If you're trying to build a pathname for a DOS command, try e.g. one of ::" | ||||
msgstr "" | ||||
"Si vous essayez de construire un chemin d'accès pour une commande DOS, " | ||||
"essayez par exemple l'un de ceux-là ::" | ||||
| ||||
#: faq/design.rst:650 | ||||
#: faq/design.rst:658 | ||||
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 ?" | ||||
| ||||
#: faq/design.rst:652 | ||||
#: faq/design.rst:660 | ||||
msgid "" | ||||
"Python has a 'with' statement that wraps the execution of a block, calling " | ||||
"code on the entrance and exit from the block. Some languages have a " | ||||
| | @ -1284,11 +1295,11 @@ msgstr "" | |||
"appelant le code sur l'entrée et la sortie du bloc. Certains langages " | ||||
"possèdent une construction qui ressemble à ceci ::" | ||||
| ||||
#: faq/design.rst:660 | ||||
#: faq/design.rst:668 | ||||
msgid "In Python, such a construct would be ambiguous." | ||||
msgstr "En Python, une telle construction serait ambiguë." | ||||
| ||||
#: faq/design.rst:662 | ||||
#: faq/design.rst:670 | ||||
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 " | ||||
| | @ -1301,7 +1312,7 @@ msgstr "" | |||
"statique --le compilateur connaît *toujours* la portée de toutes les " | ||||
"variables au moment de la compilation." | ||||
| ||||
#: faq/design.rst:667 | ||||
#: faq/design.rst:675 | ||||
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 " | ||||
| | @ -1315,11 +1326,11 @@ msgstr "" | |||
"impossible de savoir, d'une simple lecture, quel attribut est référencé : " | ||||
"s'il est local, global ou un attribut membre?" | ||||
| ||||
#: faq/design.rst:673 | ||||
#: faq/design.rst:681 | ||||
msgid "For instance, take the following incomplete snippet::" | ||||
msgstr "Prenons par exemple l'extrait incomplet suivant ::" | ||||
| ||||
#: faq/design.rst:679 | ||||
#: faq/design.rst:687 | ||||
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 " | ||||
| | @ -1333,7 +1344,7 @@ msgstr "" | |||
"\"x\" existe, sera-t-elle utilisée dans le bloc ``with`` ? Comme vous " | ||||
"voyez, la nature dynamique du Python rend ces choix beaucoup plus difficiles." | ||||
| ||||
#: faq/design.rst:685 | ||||
#: faq/design.rst:693 | ||||
msgid "" | ||||
"The primary benefit of \"with\" and similar language features (reduction of " | ||||
"code volume) can, however, easily be achieved in Python by assignment. " | ||||
| | @ -1343,11 +1354,11 @@ msgstr "" | |||
"similaires (réduction du volume de code) peut, cependant, être facilement " | ||||
"réalisé en Python par assignation. Au lieu de ::" | ||||
| ||||
#: faq/design.rst:692 | ||||
#: faq/design.rst:700 | ||||
msgid "write this::" | ||||
msgstr "écrivez ceci ::" | ||||
| ||||
#: faq/design.rst:699 | ||||
#: faq/design.rst:707 | ||||
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 " | ||||
| | @ -1357,13 +1368,13 @@ msgstr "" | |||
"car les liaisons de noms sont résolues au moment de l'exécution en Python, " | ||||
"et la deuxième version n'a besoin d'exécuter la résolution qu'une seule fois." | ||||
| ||||
#: faq/design.rst:705 | ||||
#: faq/design.rst:713 | ||||
msgid "Why are colons required for the if/while/def/class statements?" | ||||
msgstr "" | ||||
"Pourquoi les deux-points sont-ils nécessaires pour les déclarations ``if/" | ||||
"while/def/class`` ?" | ||||
| ||||
#: faq/design.rst:707 | ||||
#: faq/design.rst:715 | ||||
msgid "" | ||||
"The colon is required primarily to enhance readability (one of the results " | ||||
"of the experimental ABC language). Consider this::" | ||||
| | @ -1371,11 +1382,11 @@ msgstr "" | |||
"Le deux-points est principalement nécessaires pour améliorer la lisibilité " | ||||
"(l'un des résultats du langage expérimental ABC). Considérez ceci ::" | ||||
| ||||
#: faq/design.rst:713 | ||||
#: faq/design.rst:721 | ||||
msgid "versus ::" | ||||
msgstr "versus ::" | ||||
| ||||
#: faq/design.rst:718 | ||||
#: faq/design.rst:726 | ||||
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 " | ||||
| | @ -1385,7 +1396,7 @@ msgstr "" | |||
"aussi comment un deux-points introduit l'exemple dans cette réponse à la " | ||||
"FAQ ; c'est un usage standard en anglais." | ||||
| ||||
#: faq/design.rst:721 | ||||
#: faq/design.rst:729 | ||||
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 " | ||||
| | @ -1397,13 +1408,13 @@ msgstr "" | |||
"pour décider quand l'indentation doit être augmentée au lieu d'avoir à faire " | ||||
"une analyse plus élaborée du texte du programme." | ||||
| ||||
#: faq/design.rst:727 | ||||
#: faq/design.rst:735 | ||||
msgid "Why does Python allow commas at the end of lists and tuples?" | ||||
msgstr "" | ||||
"Pourquoi Python permet-il les virgules à la fin des listes et des *n*-" | ||||
"uplets ?" | ||||
| ||||
#: faq/design.rst:729 | ||||
#: faq/design.rst:737 | ||||
msgid "" | ||||
"Python lets you add a trailing comma at the end of lists, tuples, and " | ||||
"dictionaries::" | ||||
| | @ -1411,11 +1422,11 @@ msgstr "" | |||
"Python vous permet d'ajouter une virgule à la fin des listes, des *n*-uplets " | ||||
"et des dictionnaires ::" | ||||
| ||||
#: faq/design.rst:740 | ||||
#: faq/design.rst:748 | ||||
msgid "There are several reasons to allow this." | ||||
msgstr "Il y a plusieurs raisons d'accepter cela." | ||||
| ||||
#: faq/design.rst:742 | ||||
#: faq/design.rst:750 | ||||
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 " | ||||
| | @ -1428,7 +1439,7 @@ msgstr "" | |||
"virgule à la ligne précédente. Les lignes peuvent aussi être réorganisées " | ||||
"sans créer une erreur de syntaxe." | ||||
| ||||
#: faq/design.rst:747 | ||||
#: faq/design.rst:755 | ||||
msgid "" | ||||
"Accidentally omitting the comma can lead to errors that are hard to " | ||||
"diagnose. For example::" | ||||
| | @ -1436,7 +1447,7 @@ msgstr "" | |||
"L'omission accidentelle de la virgule peut entraîner des erreurs difficiles " | ||||
"à diagnostiquer, par exemple ::" | ||||
| ||||
#: faq/design.rst:757 | ||||
#: faq/design.rst:765 | ||||
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 " | ||||
| | @ -1446,7 +1457,7 @@ msgstr "" | |||
"trois : \"*fee*\", \"*fiefoo*\" et \"*fum*\". Toujours ajouter la virgule " | ||||
"permet d'éviter cette source d'erreur." | ||||
| ||||
#: faq/design.rst:760 | ||||
#: faq/design.rst:768 | ||||
msgid "" | ||||
"Allowing the trailing comma may also make programmatic code generation " | ||||
"easier." | ||||
| | | |||
Loading…
Add table
Add a link
Reference in a new issue