FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[View Raw Code]
[Original HTTPS Page]
python-docs-pl/reference/introduction.po at 3.14 · python/python-docs-pl · GitHub
python
python-docs-pl
Repository navigation
Code
Issues
4
(4)
Pull requests
2
(2)
Actions
Security and quality
Insights
Expand file tree
Breadcrumbs
python-docs-pl
/
reference
/
introduction.po
Copy path
More file actions
More file actions
Latest commit
History
History
History
315 lines (259 loc) · 10.4 KB
Breadcrumbs
python-docs-pl
/
reference
/
introduction.po
Copy path
File metadata and controls
315 lines (259 loc) · 10.4 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
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
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
#
SOME DESCRIPTIVE TITLE.
#
Copyright (C) 2001 Python Software Foundation
#
This file is distributed under the same license as the Python package.
#
FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#
Translators:
#
Rafael Fontenelle <rffontenelle@gmail.com>, 2026
#
#,
fuzzy
msgid ""
msgstr ""
"
Project-Id-Version
:
Python 3.14\n
"
"
Report-Msgid-Bugs-To
:
\n
"
"
POT-Creation-Date
:
2026-10-19 20:31+0000\n
"
"
PO-Revision-Date
:
2026-05-08 17:18+0000\n
"
"
Last-Translator
:
Rafael Fontenelle <rffontenelle@gmail.com>, 2026\n
"
"
Language-Team
:
Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n
"
"
MIME-Version
:
1.0\n
"
"
Content-Type
:
text/plain; charset=UTF-8\n
"
"
Content-Transfer-Encoding
:
8bit\n
"
"
Language
:
pl\n
"
"
Plural-Forms
:
nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) &&
"
"
(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 &&
"
"
n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n
"
msgid
"Introduction"
msgstr
"Wprowadzenie"
msgid
""
"This reference manual describes the Python programming language. It is not "
"intended as a tutorial."
msgstr
""
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
""
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
""
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
""
msgid
"Alternate Implementations"
msgstr
""
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
""
msgid
"Known implementations include:"
msgstr
""
msgid
"CPython"
msgstr
"CPython"
msgid
""
"This is the original and most-maintained implementation of Python, written "
"in C. New language features generally appear here first."
msgstr
""
msgid
"Jython"
msgstr
""
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
""
msgid
"Python for .NET"
msgstr
""
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
""
msgid
"IronPython"
msgstr
""
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
""
msgid
"PyPy"
msgstr
""
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
""
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
""
msgid
"Notation"
msgstr
""
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
""
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
""
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
""
msgid
""
"``name``: A name refers to another rule. Where possible, it is a link to the "
"rule's definition."
msgstr
""
msgid
""
"``TOKEN``: An uppercase name refers to a :term:`token`. For the purposes of "
"grammar definitions, tokens are the same as rules."
msgstr
""
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
""
msgid
"``'if'``: A name in single quotes denotes a :ref:`keyword <keywords>`."
msgstr
""
msgid
""
"``
\"
case
\"
``: A name in double quotes denotes a :ref:`soft-keyword <soft-"
"keywords>`."
msgstr
""
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
""
msgid
""
"``e1 e2``: Items separated only by whitespace denote a sequence. Here, "
"``e1`` must be followed by ``e2``."
msgstr
""
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
""
msgid
"``e*``: A star means zero or more repetitions of the preceding item."
msgstr
""
msgid
"``e+``: Likewise, a plus means one or more repetitions."
msgstr
""
msgid
""
"``[e]``: A phrase enclosed in square brackets means zero or one occurrences. "
"In other words, the enclosed phrase is optional."
msgstr
""
msgid
""
"``e?``: A question mark has exactly the same meaning as square brackets: the "
"preceding item is optional."
msgstr
""
msgid
"``(e)``: Parentheses are used for grouping."
msgstr
""
msgid
""
"The following notation is only used in :ref:`lexical definitions <notation-"
"lexical-vs-syntactic>`."
msgstr
""
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
""
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
""
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
""
msgid
"``&e``: a positive lookahead (that is, ``e`` is required to match)"
msgstr
""
msgid
""
"``!e``: a negative lookahead (that is, ``e`` is required *not* to match)"
msgstr
""
msgid
""
"The unary operators (``*``, ``+``, ``?``) bind as tightly as possible; the "
"vertical bar (``|``) binds most loosely."
msgstr
""
msgid
"White space is only meaningful to separate tokens."
msgstr
""
msgid
""
"Rules are normally contained on a single line, but rules that are too long "
"may be wrapped:"
msgstr
""
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
""
msgid
"This does *not* mean that there is an empty first alternative."
msgstr
""
msgid
"Lexical and Syntactic definitions"
msgstr
""
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
""
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
""
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
"BNF"
msgstr
""
msgid
"grammar"
msgstr
""
msgid
"syntax"
msgstr
""
msgid
"notation"
msgstr
""
msgid
"lexical definitions"
msgstr
""
Back
|
FazBrowse Home
|
New Git URL