@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.14\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2025-05-08 02:53-0300 \n "
15+ "POT-Creation-Date : 2025-05-09 14:19+0000 \n "
1616"PO-Revision-Date : 2021-06-28 01:49+0000\n "
1717"Last-Translator : Stan Ulbrych, 2025\n "
1818"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -51,11 +51,11 @@ msgid "Logical lines"
5151msgstr ""
5252
5353msgid ""
54- "The end of a logical line is represented by the token NEWLINE. Statements "
55- "cannot cross logical line boundaries except where NEWLINE is allowed by the "
56- "syntax (e.g., between statements in compound statements). A logical line is "
57- "constructed from one or more *physical lines* by following the explicit or "
58- "implicit *line joining* rules."
54+ "The end of a logical line is represented by the token :data:`~token. "
55+ "NEWLINE`. Statements cannot cross logical line boundaries except where :data: "
56+ "`!NEWLINE` is allowed by the syntax (e.g., between statements in compound "
57+ "statements). A logical line is constructed from one or more *physical lines* "
58+ "by following the explicit or implicit *line joining* rules."
5959msgstr ""
6060
6161msgid "Physical lines"
@@ -178,10 +178,10 @@ msgstr ""
178178
179179msgid ""
180180"A logical line that contains only spaces, tabs, formfeeds and possibly a "
181- "comment, is ignored (i.e., no NEWLINE token is generated). During "
182- "interactive input of statements, handling of a blank line may differ "
183- "depending on the implementation of the read-eval-print loop. In the "
184- "standard interactive interpreter, an entirely blank logical line (i.e. one "
181+ "comment, is ignored (i.e., no :data:`~token. NEWLINE` token is generated). "
182+ "During interactive input of statements, handling of a blank line may differ "
183+ "depending on the implementation of the read-eval-print loop. In the standard "
184+ "interactive interpreter, an entirely blank logical line (that is, one "
185185"containing not even whitespace or a comment) terminates a multi-line "
186186"statement."
187187msgstr ""
@@ -226,8 +226,8 @@ msgid ""
226226msgstr ""
227227
228228msgid ""
229- "The indentation levels of consecutive lines are used to generate INDENT and "
230- "DEDENT tokens, using a stack, as follows."
229+ "The indentation levels of consecutive lines are used to generate :data: "
230+ "`~token.INDENT` and :data:`~token. DEDENT` tokens, using a stack, as follows."
231231msgstr ""
232232
233233msgid ""
@@ -236,11 +236,12 @@ msgid ""
236236"will always be strictly increasing from bottom to top. At the beginning of "
237237"each logical line, the line's indentation level is compared to the top of "
238238"the stack. If it is equal, nothing happens. If it is larger, it is pushed on "
239- "the stack, and one INDENT token is generated. If it is smaller, it *must* "
240- "be one of the numbers occurring on the stack; all numbers on the stack that "
241- "are larger are popped off, and for each number popped off a DEDENT token is "
242- "generated. At the end of the file, a DEDENT token is generated for each "
243- "number remaining on the stack that is larger than zero."
239+ "the stack, and one :data:`!INDENT` token is generated. If it is smaller, it "
240+ "*must* be one of the numbers occurring on the stack; all numbers on the "
241+ "stack that are larger are popped off, and for each number popped off a :data:"
242+ "`!DEDENT` token is generated. At the end of the file, a :data:`!DEDENT` "
243+ "token is generated for each number remaining on the stack that is larger "
244+ "than zero."
244245msgstr ""
245246
246247msgid ""
@@ -288,20 +289,32 @@ msgid ""
288289"Except at the beginning of a logical line or in string literals, the "
289290"whitespace characters space, tab and formfeed can be used interchangeably to "
290291"separate tokens. Whitespace is needed between two tokens only if their "
291- "concatenation could otherwise be interpreted as a different token (e.g., ab "
292- "is one token, but a b is two tokens)."
292+ "concatenation could otherwise be interpreted as a different token. For "
293+ "example, ``ab`` is one token, but ``a b`` is two tokens. However, ``+a`` and "
294+ "``+ a`` both produce two tokens, ``+`` and ``a``, as ``+a`` is not a valid "
295+ "token."
296+ msgstr ""
297+
298+ msgid "End marker"
299+ msgstr ""
300+
301+ msgid ""
302+ "At the end of non-interactive input, the lexical analyzer generates an :data:"
303+ "`~token.ENDMARKER` token."
293304msgstr ""
294305
295306msgid "Other tokens"
296307msgstr ""
297308
298309msgid ""
299- "Besides NEWLINE, INDENT and DEDENT, the following categories of tokens "
300- "exist: *identifiers*, *keywords*, *literals*, *operators*, and *delimiters*. "
301- "Whitespace characters (other than line terminators, discussed earlier) are "
302- "not tokens, but serve to delimit tokens. Where ambiguity exists, a token "
303- "comprises the longest possible string that forms a legal token, when read "
304- "from left to right."
310+ "Besides :data:`~token.NEWLINE`, :data:`~token.INDENT` and :data:`~token."
311+ "DEDENT`, the following categories of tokens exist: *identifiers* and "
312+ "*keywords* (:data:`~token.NAME`), *literals* (such as :data:`~token.NUMBER` "
313+ "and :data:`~token.STRING`), and other symbols (*operators* and "
314+ "*delimiters*, :data:`~token.OP`). Whitespace characters (other than logical "
315+ "line terminators, discussed earlier) are not tokens, but serve to delimit "
316+ "tokens. Where ambiguity exists, a token comprises the longest possible "
317+ "string that forms a legal token, when read from left to right."
305318msgstr ""
306319
307320msgid "Identifiers and keywords"
0 commit comments