forked from python/python-docs-fr
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcodeop.po
More file actions
125 lines (109 loc) · 4.34 KB
/
Copy pathcodeop.po
File metadata and controls
125 lines (109 loc) · 4.34 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 1990-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 2.7\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-10-30 10:44+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/library/codeop.rst:3
msgid ":mod:`codeop` --- Compile Python code"
msgstr ""
#: ../Doc/library/codeop.rst:10
msgid ""
"The :mod:`codeop` module provides utilities upon which the Python read-eval-"
"print loop can be emulated, as is done in the :mod:`code` module. As a "
"result, you probably don't want to use the module directly; if you want to "
"include such a loop in your program you probably want to use the :mod:`code` "
"module instead."
msgstr ""
#: ../Doc/library/codeop.rst:16
msgid "There are two parts to this job:"
msgstr ""
#: ../Doc/library/codeop.rst:18
msgid ""
"Being able to tell if a line of input completes a Python statement: in "
"short, telling whether to print '``>>>``' or '``...``' next."
msgstr ""
#: ../Doc/library/codeop.rst:21
msgid ""
"Remembering which future statements the user has entered, so subsequent "
"input can be compiled with these in effect."
msgstr ""
#: ../Doc/library/codeop.rst:24
msgid ""
"The :mod:`codeop` module provides a way of doing each of these things, and a "
"way of doing them both."
msgstr ""
#: ../Doc/library/codeop.rst:27
msgid "To do just the former:"
msgstr ""
#: ../Doc/library/codeop.rst:31
msgid ""
"Tries to compile *source*, which should be a string of Python code and "
"return a code object if *source* is valid Python code. In that case, the "
"filename attribute of the code object will be *filename*, which defaults to "
"``'<input>'``. Returns ``None`` if *source* is *not* valid Python code, but "
"is a prefix of valid Python code."
msgstr ""
#: ../Doc/library/codeop.rst:37
msgid ""
"If there is a problem with *source*, an exception will be raised. :exc:"
"`SyntaxError` is raised if there is invalid Python syntax, and :exc:"
"`OverflowError` or :exc:`ValueError` if there is an invalid literal."
msgstr ""
#: ../Doc/library/codeop.rst:41
msgid ""
"The *symbol* argument determines whether *source* is compiled as a statement "
"(``'single'``, the default) or as an :term:`expression` (``'eval'``). Any "
"other value will cause :exc:`ValueError` to be raised."
msgstr ""
#: ../Doc/library/codeop.rst:47
msgid ""
"It is possible (but not likely) that the parser stops parsing with a "
"successful outcome before reaching the end of the source; in this case, "
"trailing symbols may be ignored instead of causing an error. For example, a "
"backslash followed by two newlines may be followed by arbitrary garbage. "
"This will be fixed once the API for the parser is better."
msgstr ""
#: ../Doc/library/codeop.rst:56
msgid ""
"Instances of this class have :meth:`__call__` methods identical in signature "
"to the built-in function :func:`compile`, but with the difference that if "
"the instance compiles program text containing a :mod:`__future__` statement, "
"the instance 'remembers' and compiles all subsequent program texts with the "
"statement in force."
msgstr ""
#: ../Doc/library/codeop.rst:65
msgid ""
"Instances of this class have :meth:`__call__` methods identical in signature "
"to :func:`compile_command`; the difference is that if the instance compiles "
"program text containing a ``__future__`` statement, the instance 'remembers' "
"and compiles all subsequent program texts with the statement in force."
msgstr ""
#: ../Doc/library/codeop.rst:70
msgid ""
"A note on version compatibility: the :class:`Compile` and :class:"
"`CommandCompiler` are new in Python 2.2. If you want to enable the future-"
"tracking features of 2.2 but also retain compatibility with 2.1 and earlier "
"versions of Python you can either write ::"
msgstr ""
#: ../Doc/library/codeop.rst:82
msgid ""
"which is a low-impact change, but introduces possibly unwanted global state "
"into your program, or you can write::"
msgstr ""
#: ../Doc/library/codeop.rst:92
msgid ""
"and then call ``CommandCompiler`` every time you need a fresh compiler "
"object."
msgstr ""