# Copyright (C) 2001-2018, Python Software Foundation

# For licence information, see README file.

#

msgid ""

msgstr ""

"Project-Id-Version: Python 3\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2025-10-17 09:58+0200\n"

"PO-Revision-Date: 2018-10-07 19:09+0200\n"

"Last-Translator: \n"

"Language-Team: FRENCH <traductions@lists.afpy.org>\n"

"Language: fr\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"X-Generator: Poedit 2.1.1\n"

#: reference/introduction.rst:6

msgid "Introduction"

msgstr "Introduction"

#: reference/introduction.rst:8

msgid ""

"This reference manual describes the Python programming language. It is not "

"intended as a tutorial."

msgstr ""

"Ce manuel de référence décrit le langage de programmation Python. Il n'a pas "

"vocation à être un tutoriel."

#: reference/introduction.rst:11

msgid ""

"While I am trying to be as precise as possible, I chose to use English "

"rather than formal specifications for everything except syntax and lexical "

"analysis. This should make the document more understandable to the average "

"reader, but will leave room for ambiguities. Consequently, if you were "

"coming from Mars and tried to re-implement Python from this document alone, "

"you might have to guess things and in fact you would probably end up "

"implementing quite a different language. On the other hand, if you are using "

"Python and wonder what the precise rules about a particular area of the "

"language are, you should definitely be able to find them here. If you would "

"like to see a more formal definition of the language, maybe you could "

"volunteer your time --- or invent a cloning machine :-)."

msgstr ""

"Nous essayons d'être le plus précis possible et nous utilisons le français "

"(NdT : ou l’anglais pour les parties qui ne sont pas encore traduites) "

"plutôt que des spécifications formelles, sauf pour la syntaxe et l’analyse "

"lexicale. Nous espérons ainsi rendre ce document plus compréhensible pour un "

"grand nombre de lecteurs, même si cela laisse un peu de place à l’ambiguïté. "

"En conséquence, si vous arrivez de Mars et que vous essayez de ré-"

"implémenter Python à partir de cet unique document, vous devrez faire des "

"hypothèses et, finalement, vous aurez certainement implémenté un langage "

"sensiblement différent. D’un autre côté, si vous utilisez Python et que vous "

"vous demandez quelles règles s’appliquent pour telle partie du langage, vous "

"devriez trouver une réponse satisfaisante ici. Si vous souhaitez voir une "

"définition plus formelle du langage, nous acceptons toutes les bonnes "

"volontés (ou bien inventez une machine pour nous cloner ☺)."

#: reference/introduction.rst:23

msgid ""

"It is dangerous to add too many implementation details to a language "

"reference document --- the implementation may change, and other "

"implementations of the same language may work differently. On the other "

"hand, CPython is the one Python implementation in widespread use (although "

"alternate implementations continue to gain support), and its particular "

"quirks are sometimes worth being mentioned, especially where the "

"implementation imposes additional limitations. Therefore, you'll find short "

"\"implementation notes\" sprinkled throughout the text."

msgstr ""

"S’agissant du manuel de référence d’un langage, il est dangereux de rentrer "

"profondément dans les détails d’implémentation ; l’implémentation peut "

"changer et d’autres implémentations du même langage peuvent fonctionner "

"différemment. En même temps, CPython est l’implémentation de Python la plus "

"répandue (bien que d’autres implémentations gagnent en popularité) et "

"certaines de ses bizarreries méritent parfois d’être mentionnées, en "

"particulier lorsque l’implémentation impose des limitations supplémentaires. "

"Par conséquent, vous trouvez de courtes \"notes d’implémentation\" "

"saupoudrées dans le texte."

#: reference/introduction.rst:32

msgid ""

"Every Python implementation comes with a number of built-in and standard "

"modules. These are documented in :ref:`library-index`. A few built-in "

"modules are mentioned when they interact in a significant way with the "

"language definition."

msgstr ""

"Chaque implémentation de Python est livrée avec un certain nombre de modules "

"natifs. Ceux-ci sont documentés dans :ref:`library-index`. Quelques modules "

"natifs sont mentionnés quand ils interagissent significativement avec la "

"définition du langage."

#: reference/introduction.rst:41

msgid "Alternate Implementations"

msgstr "Autres implémentations"

#: reference/introduction.rst:43

msgid ""

"Though there is one Python implementation which is by far the most popular, "

"there are some alternate implementations which are of particular interest to "

"different audiences."

msgstr ""

"Bien qu’il existe une implémentation Python qui soit de loin la plus "

"populaire, il existe d’autres implémentations qui présentent un intérêt "

"particulier pour différents publics."

#: reference/introduction.rst:47

msgid "Known implementations include:"

msgstr "Parmi les implémentations les plus connues, nous pouvons citer :"

#: reference/introduction.rst:49

msgid "CPython"

msgstr "CPython"

#: reference/introduction.rst:50

msgid ""

"This is the original and most-maintained implementation of Python, written "

"in C. New language features generally appear here first."

msgstr ""

"C’est l’implémentation originelle et la plus entretenue de Python, écrite en "

"C. Elle implémente généralement en premier les nouvelles fonctionnalités du "

"langage."

#: reference/introduction.rst:53

msgid "Jython"

msgstr "Jython"

#: reference/introduction.rst:54

msgid ""

"Python implemented in Java. This implementation can be used as a scripting "

"language for Java applications, or can be used to create applications using "

"the Java class libraries. It is also often used to create tests for Java "

"libraries. More information can be found at `the Jython website <https://"

"www.jython.org/>`_."

msgstr ""

"Python implémenté en Java. Cette implémentation peut être utilisée comme "

"langage de script pour les applications Java ou pour créer des applications "

"utilisant des bibliothèques Java. Elle est également souvent utilisée pour "

"créer des tests de bibliothèques Java. Plus d’informations peuvent être "

"trouvées sur `the Jython website <https://www.jython.org/>`_ (site en "

"anglais)."

#: reference/introduction.rst:59

msgid "Python for .NET"

msgstr "Python pour .NET"

#: reference/introduction.rst:60

msgid ""

"This implementation actually uses the CPython implementation, but is a "

"managed .NET application and makes .NET libraries available. It was created "

"by Brian Lloyd. For more information, see the `Python for .NET home page "

"<https://pythonnet.github.io/>`_."

msgstr ""

"Cette implémentation utilise en fait l’implémentation CPython, mais c’est "

"une application .NET et permet un accès aux bibliothèques .NET. Elle a été "

"créée par Brian Lloyd. Pour plus d’informations, consultez la page d’accueil "

"`Python pour .NET <https://pythonnet.github.io/>`_ (site en anglais)."

#: reference/introduction.rst:65

msgid "IronPython"

msgstr "IronPython"

#: reference/introduction.rst:66

msgid ""

"An alternate Python for .NET. Unlike Python.NET, this is a complete Python "

"implementation that generates IL, and compiles Python code directly to .NET "

"assemblies. It was created by Jim Hugunin, the original creator of Jython. "

"For more information, see `the IronPython website <https://ironpython.net/"

">`_."

msgstr ""

"Un autre Python pour .NET. Contrairement à Python.NET, il s’agit d’une "

"implémentation Python complète qui génère du code intermédiaire (IL) .NET et "

"compile le code Python directement en assemblages .NET. Il a été créé par "

"Jim Hugunin, le programmeur à l’origine de Jython. Pour plus d’informations, "

"voir `the IronPython website <https://ironpython.net/>`_ (site en anglais)."

#: reference/introduction.rst:71

msgid "PyPy"

msgstr "PyPy"

#: reference/introduction.rst:72

#, fuzzy

msgid ""

"An implementation of Python written completely in Python. It supports "

"several advanced features not found in other implementations like stackless "

"support and a Just in Time compiler. One of the goals of the project is to "

"encourage experimentation with the language itself by making it easier to "

"modify the interpreter (since it is written in Python). Additional "

"information is available on `the PyPy project's home page <https://pypy.org/"

">`_."

msgstr ""

"Une implémentation de Python complètement écrite en Python. Elle apporte des "

"fonctionnalités avancées introuvables dans d'autres implémentations, telles "

"que le fonctionnement sans pile (*stackless* en anglais) et un compilateur à "

"la volée (*Just in Time compiler* en anglais). L'un des objectifs du projet "

"est d'encourager l'expérimentation du langage lui-même en facilitant la "

"modification de l'interpréteur (puisqu'il est écrit en Python). Des "

"informations complémentaires sont disponibles sur la `page d'accueil du "

"projet PyPy <http://pypy.org/>`_ (site en anglais)."

#: reference/introduction.rst:79

msgid ""

"Each of these implementations varies in some way from the language as "

"documented in this manual, or introduces specific information beyond what's "

"covered in the standard Python documentation. Please refer to the "

"implementation-specific documentation to determine what else you need to "

"know about the specific implementation you're using."

msgstr ""

"Chacune de ces implémentations diffère d'une manière ou d'une autre par "

"rapport au langage décrit dans ce manuel, ou comporte des spécificités que "

"la documentation standard de Python ne couvre pas. Reportez-vous à la "

"documentation spécifique à l'implémentation pour déterminer ce que vous "

"devez savoir sur l'implémentation que vous utilisez."

#: reference/introduction.rst:89

msgid "Notation"

msgstr "Notations"

#: reference/introduction.rst:93

#, fuzzy

msgid ""

"The descriptions of lexical analysis and syntax use a grammar notation that "

"is a mixture of `EBNF <https://en.wikipedia.org/wiki/"

"Extended_Backus%E2%80%93Naur_form>`_ and `PEG <https://en.wikipedia.org/wiki/"

"Parsing_expression_grammar>`_. For example:"

msgstr ""

"Les descriptions de l'analyse lexicale et de la syntaxe utilisent une "

"notation de grammaire BNF modifiée. Le style utilisé est le suivant :"

#: reference/introduction.rst:106

#, fuzzy

msgid ""

"In this example, the first line says that a ``name`` is a ``letter`` "

"followed by a sequence of zero or more ``letter``\\ s, ``digit``\\ s, and "

"underscores. A ``letter`` in turn is any of the single characters ``'a'`` "

"through ``'z'`` and ``A`` through ``Z``; a ``digit`` is a single character "

"from ``0`` to ``9``."

msgstr ""

"La première ligne indique qu'un ``name`` est un ``lc_letter`` suivi d'une "

"suite de zéro ou plus ``lc_letter``\\s ou tiret bas. Un ``lc_letter`` est, à "

"son tour, l'un des caractères ``'a'`` à ``'z'`` (cette règle est "

"effectivement respectée pour les noms définis dans les règles lexicales et "

"grammaticales de ce document)."

#: reference/introduction.rst:112

msgid ""

"Each rule begins with a name (which identifies the rule that's being "

"defined) followed by a colon, ``:``. The definition to the right of the "

"colon uses the following syntax elements:"

msgstr ""

#: reference/introduction.rst:116

msgid ""

"``name``: A name refers to another rule. Where possible, it is a link to the "

"rule's definition."

msgstr ""

#: reference/introduction.rst:119

msgid ""

"``TOKEN``: An uppercase name refers to a :term:`token`. For the purposes of "

"grammar definitions, tokens are the same as rules."

msgstr ""

#: reference/introduction.rst:122

msgid ""

"``\"text\"``, ``'text'``: Text in single or double quotes must match "

"literally (without the quotes). The type of quote is chosen according to the "

"meaning of ``text``:"

msgstr ""

#: reference/introduction.rst:126

msgid "``'if'``: A name in single quotes denotes a :ref:`keyword <keywords>`."

msgstr ""

#: reference/introduction.rst:127

msgid ""

"``\"case\"``: A name in double quotes denotes a :ref:`soft-keyword <soft-"

"keywords>`."

msgstr ""

#: reference/introduction.rst:129

msgid ""

"``'@'``: A non-letter symbol in single quotes denotes "

"an :py:data:`~token.OP` token, that is, a :ref:`delimiter <delimiters>` "

"or :ref:`operator <operators>`."

msgstr ""

#: reference/introduction.rst:133

msgid ""

"``e1 e2``: Items separated only by whitespace denote a sequence. Here, "

"``e1`` must be followed by ``e2``."

msgstr ""

#: reference/introduction.rst:135

msgid ""

"``e1 | e2``: A vertical bar is used to separate alternatives. It denotes "

"PEG's \"ordered choice\": if ``e1`` matches, ``e2`` is not considered. In "

"traditional PEG grammars, this is written as a slash, ``/``, rather than a "

"vertical bar. See :pep:`617` for more background and details."

msgstr ""

#: reference/introduction.rst:141

msgid "``e*``: A star means zero or more repetitions of the preceding item."

msgstr ""

#: reference/introduction.rst:142

msgid "``e+``: Likewise, a plus means one or more repetitions."

msgstr ""

#: reference/introduction.rst:143

msgid ""

"``[e]``: A phrase enclosed in square brackets means zero or one occurrences. "

"In other words, the enclosed phrase is optional."

msgstr ""

#: reference/introduction.rst:145

msgid ""

"``e?``: A question mark has exactly the same meaning as square brackets: the "

"preceding item is optional."

msgstr ""

#: reference/introduction.rst:147

msgid "``(e)``: Parentheses are used for grouping."

msgstr ""

#: reference/introduction.rst:149

msgid ""

"The following notation is only used in :ref:`lexical definitions <notation-"

"lexical-vs-syntactic>`."

msgstr ""

#: reference/introduction.rst:152

msgid ""

"``\"a\"...\"z\"``: Two literal characters separated by three dots mean a "

"choice of any single character in the given (inclusive) range of ASCII "

"characters."

msgstr ""

#: reference/introduction.rst:154

msgid ""

"``<...>``: A phrase between angular brackets gives an informal description "

"of the matched symbol (for example, ``<any ASCII character except \"\\"

"\">``), or an abbreviation that is defined in nearby text (for example, "

"``<Lu>``)."

msgstr ""

#: reference/introduction.rst:160

msgid ""

"Some definitions also use *lookaheads*, which indicate that an element must "

"(or must not) match at a given position, but without consuming any input:"

msgstr ""

#: reference/introduction.rst:163

msgid "``&e``: a positive lookahead (that is, ``e`` is required to match)"

msgstr ""

#: reference/introduction.rst:164

msgid ""

"``!e``: a negative lookahead (that is, ``e`` is required *not* to match)"

msgstr ""

#: reference/introduction.rst:166

msgid ""

"The unary operators (``*``, ``+``, ``?``) bind as tightly as possible; the "

"vertical bar (``|``) binds most loosely."

msgstr ""

#: reference/introduction.rst:169

msgid "White space is only meaningful to separate tokens."

msgstr ""

#: reference/introduction.rst:171

msgid ""

"Rules are normally contained on a single line, but rules that are too long "

"may be wrapped:"

msgstr ""

#: reference/introduction.rst:180

msgid ""

"Alternatively, rules may be formatted with the first line ending at the "

"colon, and each alternative beginning with a vertical bar on a new line. For "

"example:"

msgstr ""

#: reference/introduction.rst:195

msgid "This does *not* mean that there is an empty first alternative."

msgstr ""

#: reference/introduction.rst:202

msgid "Lexical and Syntactic definitions"

msgstr ""

#: reference/introduction.rst:204

#, fuzzy

msgid ""

"There is some difference between *lexical* and *syntactic* analysis: "

"the :term:`lexical analyzer` operates on the individual characters of the "

"input source, while the *parser* (syntactic analyzer) operates on the stream "

"of :term:`tokens <token>` generated by the lexical analysis. However, in "

"some cases the exact boundary between the two phases is a CPython "

"implementation detail."

msgstr ""

"Même si la notation utilisée est presque la même, il existe une grande "

"différence entre la signification des définitions lexicales et syntaxiques : "

"une définition lexicale opère sur les caractères individuels de l'entrée, "

"tandis qu'une définition syntaxique opère sur le flux de lexèmes générés par "

"l'analyse lexicale. Toutes les notations sous la forme BNF dans le chapitre "

"suivant (« Analyse lexicale ») sont des définitions lexicales ; les "

"notations dans les chapitres suivants sont des définitions syntaxiques."

#: reference/introduction.rst:211

msgid ""

"The practical difference between the two is that in *lexical* definitions, "

"all whitespace is significant. The lexical analyzer :ref:`discards "

"<whitespace>` all whitespace that is not converted to tokens "

"like :data:`token.INDENT` or :data:`~token.NEWLINE`. *Syntactic* definitions "

"then use these tokens, rather than source characters."

msgstr ""

#: reference/introduction.rst:217

msgid ""

"This documentation uses the same BNF grammar for both styles of definitions. "

"All uses of BNF in the next chapter (:ref:`lexical`) are lexical "

"definitions; uses in subsequent chapters are syntactic definitions."

msgstr ""

#~ msgid ""

#~ "Each rule begins with a name (which is the name defined by the rule) and "

#~ "``::=``. A vertical bar (``|``) is used to separate alternatives; it is "

#~ "the least binding operator in this notation. A star (``*``) means zero "

#~ "or more repetitions of the preceding item; likewise, a plus (``+``) means "

#~ "one or more repetitions, and a phrase enclosed in square brackets "

#~ "(``[ ]``) means zero or one occurrences (in other words, the enclosed "

#~ "phrase is optional). The ``*`` and ``+`` operators bind as tightly as "

#~ "possible; parentheses are used for grouping. Literal strings are "

#~ "enclosed in quotes. White space is only meaningful to separate tokens. "

#~ "Rules are normally contained on a single line; rules with many "

#~ "alternatives may be formatted alternatively with each line after the "

#~ "first beginning with a vertical bar."

#~ msgstr ""

#~ "Chaque règle commence par un nom (qui est le nom que la règle définit) et "

#~ "``::=``. Une barre verticale (``|``) est utilisée pour séparer les "

#~ "alternatives ; c'est l'opérateur le moins prioritaire de cette notation. "

#~ "Une étoile (``*``) signifie zéro ou plusieurs répétitions de l'élément "

#~ "précédent ; de même, un plus (``+``) signifie une ou plusieurs "

#~ "répétitions, et une expression entre crochets (``[ ]``) signifie zéro ou "

#~ "une occurrence (en d'autres termes, l'expression encadrée est "

#~ "facultative). Les opérateurs ``*`` et ``+`` agissent aussi étroitement "

#~ "que possible ; les parenthèses sont utilisées pour le regroupement. Les "

#~ "chaînes littérales sont entourées de guillemets anglais ``\"``. L'espace "

#~ "n'est utilisée que pour séparer les lexèmes. Les règles sont normalement "

#~ "contenues sur une seule ligne ; les règles avec de nombreuses "

#~ "alternatives peuvent être formatées avec chaque ligne représentant une "

#~ "alternative (et donc débutant par une barre verticale, sauf la première)."

#~ msgid ""

#~ "In lexical definitions (as the example above), two more conventions are "

#~ "used: Two literal characters separated by three dots mean a choice of any "

#~ "single character in the given (inclusive) range of ASCII characters. A "

#~ "phrase between angular brackets (``<...>``) gives an informal description "

#~ "of the symbol defined; e.g., this could be used to describe the notion of "

#~ "'control character' if needed."

#~ msgstr ""

#~ "Dans les définitions lexicales (comme dans l'exemple ci-dessus), deux "

#~ "autres conventions sont utilisées : deux caractères littéraux séparés par "

#~ "des points de suspension signifient le choix d'un seul caractère dans la "

#~ "plage donnée (en incluant les bornes) de caractères ASCII. Une phrase "

#~ "entre les signes inférieur et supérieur (``<...>``) donne une description "

#~ "informelle du symbole défini ; par exemple, pour décrire la notion de "

#~ "\"caractère de contrôle\" si nécessaire."

#~ msgid "BNF"

#~ msgstr "BNF"

#~ msgid "notation"

#~ msgstr "notation"