lexical_analysis.po

# 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:
# python-doc bot, 2025
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-08-22 12:07+0200\n"
"PO-Revision-Date: 2025-09-16 00:02+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: ../../reference/lexical_analysis.rst:6
msgid "Lexical analysis"
msgstr ""

#: ../../reference/lexical_analysis.rst:10
msgid ""
"A Python program is read by a *parser*.  Input to the parser is a stream of :"
"term:`tokens <token>`, generated by the *lexical analyzer* (also known as "
"the *tokenizer*). This chapter describes how the lexical analyzer produces "
"these tokens."
msgstr ""

#: ../../reference/lexical_analysis.rst:15
msgid ""
"The lexical analyzer determines the program text's :ref:`encoding "
"<encodings>` (UTF-8 by default), and decodes the text into :ref:`source "
"characters <lexical-source-character>`. If the text cannot be decoded, a :"
"exc:`SyntaxError` is raised."
msgstr ""

#: ../../reference/lexical_analysis.rst:20
msgid ""
"Next, the lexical analyzer uses the source characters to generate a stream "
"of tokens. The type of a generated token generally depends on the next "
"source character to be processed. Similarly, other special behavior of the "
"analyzer depends on the first source character that hasn't yet been "
"processed. The following table gives a quick summary of these source "
"characters, with links to sections that contain more information."
msgstr ""

#: ../../reference/lexical_analysis.rst:30
msgid "Character"
msgstr "Zeichen"

#: ../../reference/lexical_analysis.rst:31
msgid "Next token (or other relevant documentation)"
msgstr ""

#: ../../reference/lexical_analysis.rst:33
#: ../../reference/lexical_analysis.rst:266
msgid "space"
msgstr "Leerzeichen"

#: ../../reference/lexical_analysis.rst:34
#: ../../reference/lexical_analysis.rst:266
msgid "tab"
msgstr ""

#: ../../reference/lexical_analysis.rst:35
msgid "formfeed"
msgstr ""

#: ../../reference/lexical_analysis.rst:36
msgid ":ref:`Whitespace <whitespace>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:38
msgid "CR, LF"
msgstr ""

#: ../../reference/lexical_analysis.rst:39
msgid ":ref:`New line <line-structure>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:40
msgid ":ref:`Indentation <indentation>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:42
msgid "backslash (``\\``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:43
msgid ":ref:`Explicit line joining <explicit-joining>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:44
msgid "(Also significant in :ref:`string escape sequences <escape-sequences>`)"
msgstr ""

#: ../../reference/lexical_analysis.rst:46
msgid "hash (``#``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:47
msgid ":ref:`Comment <comments>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:49
msgid "quote (``'``, ``\"``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:50
msgid ":ref:`String literal <strings>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:52
msgid "ASCII letter (``a``-``z``, ``A``-``Z``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:53
msgid "non-ASCII character"
msgstr ""

#: ../../reference/lexical_analysis.rst:54
#: ../../reference/lexical_analysis.rst:58
msgid ":ref:`Name <identifiers>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:55
msgid "Prefixed :ref:`string or bytes literal <strings>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:57
msgid "underscore (``_``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:59
msgid "(Can also be part of :ref:`numeric literals <numbers>`)"
msgstr ""

#: ../../reference/lexical_analysis.rst:61
msgid "number (``0``-``9``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:62
#: ../../reference/lexical_analysis.rst:65
msgid ":ref:`Numeric literal <numbers>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:64
msgid "dot (``.``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:66
msgid ":ref:`Operator <operators>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:68
msgid "question mark (``?``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:69
msgid "dollar (``$``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:74
msgid "backquote (``​`​``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:75
msgid "control character"
msgstr ""

#: ../../reference/lexical_analysis.rst:76
msgid "Error (outside string literals and comments)"
msgstr ""

#: ../../reference/lexical_analysis.rst:78
msgid "other printing character"
msgstr ""

#: ../../reference/lexical_analysis.rst:79
msgid ":ref:`Operator or delimiter <operators>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:81
msgid "end of file"
msgstr ""

#: ../../reference/lexical_analysis.rst:82
msgid ":ref:`End marker <endmarker-token>`"
msgstr ""

#: ../../reference/lexical_analysis.rst:88
msgid "Line structure"
msgstr ""

#: ../../reference/lexical_analysis.rst:92
msgid "A Python program is divided into a number of *logical lines*."
msgstr ""

#: ../../reference/lexical_analysis.rst:98
msgid "Logical lines"
msgstr ""

#: ../../reference/lexical_analysis.rst:102
msgid ""
"The end of a logical line is represented by the token :data:`~token."
"NEWLINE`. Statements cannot cross logical line boundaries except where :data:"
"`!NEWLINE` is allowed by the syntax (e.g., between statements in compound "
"statements). A logical line is constructed from one or more *physical lines* "
"by following the :ref:`explicit <explicit-joining>` or :ref:`implicit "
"<implicit-joining>` *line joining* rules."
msgstr ""

#: ../../reference/lexical_analysis.rst:113
msgid "Physical lines"
msgstr ""

#: ../../reference/lexical_analysis.rst:115
msgid ""
"A physical line is a sequence of characters terminated by one the following "
"end-of-line sequences:"
msgstr ""

#: ../../reference/lexical_analysis.rst:118
msgid "the Unix form using ASCII LF (linefeed),"
msgstr ""

#: ../../reference/lexical_analysis.rst:119
msgid ""
"the Windows form using the ASCII sequence CR LF (return followed by "
"linefeed),"
msgstr ""

#: ../../reference/lexical_analysis.rst:120
msgid "the '`Classic Mac OS`__' form using the ASCII CR (return) character."
msgstr ""

#: ../../reference/lexical_analysis.rst:124
msgid ""
"Regardless of platform, each of these sequences is replaced by a single "
"ASCII LF (linefeed) character. (This is done even inside :ref:`string "
"literals <strings>`.) Each line can use any of the sequences; they do not "
"need to be consistent within a file."
msgstr ""

#: ../../reference/lexical_analysis.rst:130
msgid ""
"The end of input also serves as an implicit terminator for the final "
"physical line."
msgstr ""

#: ../../reference/lexical_analysis.rst:133
msgid "Formally:"
msgstr "Formal:"

#: ../../reference/lexical_analysis.rst:144
msgid "Comments"
msgstr ""

#: ../../reference/lexical_analysis.rst:149
msgid ""
"A comment starts with a hash character (``#``) that is not part of a string "
"literal, and ends at the end of the physical line.  A comment signifies the "
"end of the logical line unless the implicit line joining rules are invoked. "
"Comments are ignored by the syntax."
msgstr ""

#: ../../reference/lexical_analysis.rst:158
msgid "Encoding declarations"
msgstr ""

#: ../../reference/lexical_analysis.rst:163
msgid ""
"If a comment in the first or second line of the Python script matches the "
"regular expression ``coding[=:]\\s*([-\\w.]+)``, this comment is processed "
"as an encoding declaration; the first group of this expression names the "
"encoding of the source code file. The encoding declaration must appear on a "
"line of its own. If it is the second line, the first line must also be a "
"comment-only line. The recommended forms of an encoding expression are ::"
msgstr ""

#: ../../reference/lexical_analysis.rst:170
msgid "# -*- coding: <encoding-name> -*-"
msgstr ""

#: ../../reference/lexical_analysis.rst:172
msgid "which is recognized also by GNU Emacs, and ::"
msgstr ""

#: ../../reference/lexical_analysis.rst:174
msgid "# vim:fileencoding=<encoding-name>"
msgstr ""

#: ../../reference/lexical_analysis.rst:176
msgid "which is recognized by Bram Moolenaar's VIM."
msgstr ""

#: ../../reference/lexical_analysis.rst:178
msgid ""
"If no encoding declaration is found, the default encoding is UTF-8.  If the "
"implicit or explicit encoding of a file is UTF-8, an initial UTF-8 byte-"
"order mark (``b'\\xef\\xbb\\xbf'``) is ignored rather than being a syntax "
"error."
msgstr ""

#: ../../reference/lexical_analysis.rst:182
msgid ""
"If an encoding is declared, the encoding name must be recognized by Python "
"(see :ref:`standard-encodings`). The encoding is used for all lexical "
"analysis, including string literals, comments and identifiers."
msgstr ""

#: ../../reference/lexical_analysis.rst:189
msgid ""
"All lexical analysis, including string literals, comments and identifiers, "
"works on Unicode text decoded using the source encoding. Any Unicode code "
"point, except the NUL control character, can appear in Python source."
msgstr ""

#: ../../reference/lexical_analysis.rst:203
msgid "Explicit line joining"
msgstr ""

#: ../../reference/lexical_analysis.rst:207
msgid ""
"Two or more physical lines may be joined into logical lines using backslash "
"characters (``\\``), as follows: when a physical line ends in a backslash "
"that is not part of a string literal or comment, it is joined with the "
"following forming a single logical line, deleting the backslash and the "
"following end-of-line character.  For example::"
msgstr ""

#: ../../reference/lexical_analysis.rst:213
msgid ""
"if 1900 < year < 2100 and 1 <= month <= 12 \\\n"
"   and 1 <= day <= 31 and 0 <= hour < 24 \\\n"
"   and 0 <= minute < 60 and 0 <= second < 60:   # Looks like a valid date\n"
"        return 1"
msgstr ""

#: ../../reference/lexical_analysis.rst:218
msgid ""
"A line ending in a backslash cannot carry a comment.  A backslash does not "
"continue a comment.  A backslash does not continue a token except for string "
"literals (i.e., tokens other than string literals cannot be split across "
"physical lines using a backslash).  A backslash is illegal elsewhere on a "
"line outside a string literal."
msgstr ""

#: ../../reference/lexical_analysis.rst:228
msgid "Implicit line joining"
msgstr ""

#: ../../reference/lexical_analysis.rst:230
msgid ""
"Expressions in parentheses, square brackets or curly braces can be split "
"over more than one physical line without using backslashes. For example::"
msgstr ""

#: ../../reference/lexical_analysis.rst:233
msgid ""
"month_names = ['Januari', 'Februari', 'Maart',      # These are the\n"
"               'April',   'Mei',      'Juni',       # Dutch names\n"
"               'Juli',    'Augustus', 'September',  # for the months\n"
"               'Oktober', 'November', 'December']   # of the year"
msgstr ""

#: ../../reference/lexical_analysis.rst:238
msgid ""
"Implicitly continued lines can carry comments.  The indentation of the "
"continuation lines is not important.  Blank continuation lines are allowed. "
"There is no NEWLINE token between implicit continuation lines.  Implicitly "
"continued lines can also occur within triple-quoted strings (see below); in "
"that case they cannot carry comments."
msgstr ""

#: ../../reference/lexical_analysis.rst:248
msgid "Blank lines"
msgstr ""

#: ../../reference/lexical_analysis.rst:252
msgid ""
"A logical line that contains only spaces, tabs, formfeeds and possibly a "
"comment, is ignored (i.e., no :data:`~token.NEWLINE` token is generated). "
"During interactive input of statements, handling of a blank line may differ "
"depending on the implementation of the read-eval-print loop. In the standard "
"interactive interpreter, an entirely blank logical line (that is, one "
"containing not even whitespace or a comment) terminates a multi-line "
"statement."
msgstr ""

#: ../../reference/lexical_analysis.rst:264
msgid "Indentation"
msgstr ""

#: ../../reference/lexical_analysis.rst:268
msgid ""
"Leading whitespace (spaces and tabs) at the beginning of a logical line is "
"used to compute the indentation level of the line, which in turn is used to "
"determine the grouping of statements."
msgstr ""

#: ../../reference/lexical_analysis.rst:272
msgid ""
"Tabs are replaced (from left to right) by one to eight spaces such that the "
"total number of characters up to and including the replacement is a multiple "
"of eight (this is intended to be the same rule as used by Unix).  The total "
"number of spaces preceding the first non-blank character then determines the "
"line's indentation.  Indentation cannot be split over multiple physical "
"lines using backslashes; the whitespace up to the first backslash determines "
"the indentation."
msgstr ""

#: ../../reference/lexical_analysis.rst:280
msgid ""
"Indentation is rejected as inconsistent if a source file mixes tabs and "
"spaces in a way that makes the meaning dependent on the worth of a tab in "
"spaces; a :exc:`TabError` is raised in that case."
msgstr ""

#: ../../reference/lexical_analysis.rst:284
msgid ""
"**Cross-platform compatibility note:** because of the nature of text editors "
"on non-UNIX platforms, it is unwise to use a mixture of spaces and tabs for "
"the indentation in a single source file.  It should also be noted that "
"different platforms may explicitly limit the maximum indentation level."
msgstr ""

#: ../../reference/lexical_analysis.rst:289
msgid ""
"A formfeed character may be present at the start of the line; it will be "
"ignored for the indentation calculations above.  Formfeed characters "
"occurring elsewhere in the leading whitespace have an undefined effect (for "
"instance, they may reset the space count to zero)."
msgstr ""

#: ../../reference/lexical_analysis.rst:296
msgid ""
"The indentation levels of consecutive lines are used to generate :data:"
"`~token.INDENT` and :data:`~token.DEDENT` tokens, using a stack, as follows."
msgstr ""

#: ../../reference/lexical_analysis.rst:300
msgid ""
"Before the first line of the file is read, a single zero is pushed on the "
"stack; this will never be popped off again.  The numbers pushed on the stack "
"will always be strictly increasing from bottom to top.  At the beginning of "
"each logical line, the line's indentation level is compared to the top of "
"the stack. If it is equal, nothing happens. If it is larger, it is pushed on "
"the stack, and one :data:`!INDENT` token is generated.  If it is smaller, it "
"*must* be one of the numbers occurring on the stack; all numbers on the "
"stack that are larger are popped off, and for each number popped off a :data:"
"`!DEDENT` token is generated. At the end of the file, a :data:`!DEDENT` "
"token is generated for each number remaining on the stack that is larger "
"than zero."
msgstr ""

#: ../../reference/lexical_analysis.rst:311
msgid ""
"Here is an example of a correctly (though confusingly) indented piece of "
"Python code::"
msgstr ""

#: ../../reference/lexical_analysis.rst:314
msgid ""
"def perm(l):\n"
"        # Compute the list of all permutations of l\n"
"    if len(l) <= 1:\n"
"                  return [l]\n"
"    r = []\n"
"    for i in range(len(l)):\n"
"             s = l[:i] + l[i+1:]\n"
"             p = perm(s)\n"
"             for x in p:\n"
"              r.append(l[i:i+1] + x)\n"
"    return r"
msgstr ""

#: ../../reference/lexical_analysis.rst:326
msgid "The following example shows various indentation errors::"
msgstr ""

#: ../../reference/lexical_analysis.rst:328
msgid ""
" def perm(l):                       # error: first line indented\n"
"for i in range(len(l)):             # error: not indented\n"
"    s = l[:i] + l[i+1:]\n"
"        p = perm(l[:i] + l[i+1:])   # error: unexpected indent\n"
"        for x in p:\n"
"                r.append(l[i:i+1] + x)\n"
"            return r                # error: inconsistent dedent"
msgstr ""

#: ../../reference/lexical_analysis.rst:336
msgid ""
"(Actually, the first three errors are detected by the parser; only the last "
"error is found by the lexical analyzer --- the indentation of ``return r`` "
"does not match a level popped off the stack.)"
msgstr ""

#: ../../reference/lexical_analysis.rst:344
msgid "Whitespace between tokens"
msgstr ""

#: ../../reference/lexical_analysis.rst:346
msgid ""
"Except at the beginning of a logical line or in string literals, the "
"whitespace characters space, tab and formfeed can be used interchangeably to "
"separate tokens:"
msgstr ""

#: ../../reference/lexical_analysis.rst:356
msgid ""
"Whitespace is needed between two tokens only if their concatenation could "
"otherwise be interpreted as a different token. For example, ``ab`` is one "
"token, but ``a b`` is two tokens. However, ``+a`` and ``+ a`` both produce "
"two tokens, ``+`` and ``a``, as ``+a`` is not a valid token."
msgstr ""

#: ../../reference/lexical_analysis.rst:365
msgid "End marker"
msgstr ""

#: ../../reference/lexical_analysis.rst:367
msgid ""
"At the end of non-interactive input, the lexical analyzer generates an :data:"
"`~token.ENDMARKER` token."
msgstr ""

#: ../../reference/lexical_analysis.rst:374
msgid "Other tokens"
msgstr ""

#: ../../reference/lexical_analysis.rst:376
msgid ""
"Besides :data:`~token.NEWLINE`, :data:`~token.INDENT` and :data:`~token."
"DEDENT`, the following categories of tokens exist: *identifiers* and "
"*keywords* (:data:`~token.NAME`), *literals* (such as :data:`~token.NUMBER` "
"and :data:`~token.STRING`), and other symbols (*operators* and "
"*delimiters*, :data:`~token.OP`). Whitespace characters (other than logical "
"line terminators, discussed earlier) are not tokens, but serve to delimit "
"tokens. Where ambiguity exists, a token comprises the longest possible "
"string that forms a legal token, when read from left to right."
msgstr ""

#: ../../reference/lexical_analysis.rst:390
msgid "Names (identifiers and keywords)"
msgstr ""

#: ../../reference/lexical_analysis.rst:394
msgid ""
":data:`~token.NAME` tokens represent *identifiers*, *keywords*, and *soft "
"keywords*."
msgstr ""

#: ../../reference/lexical_analysis.rst:397
msgid "Names are composed of the following characters:"
msgstr ""

#: ../../reference/lexical_analysis.rst:399
msgid "uppercase and lowercase letters (``A-Z`` and ``a-z``),"
msgstr ""

#: ../../reference/lexical_analysis.rst:400
msgid "the underscore (``_``),"
msgstr ""

#: ../../reference/lexical_analysis.rst:401
msgid ""
"digits (``0`` through ``9``), which cannot appear as the first character, and"
msgstr ""

#: ../../reference/lexical_analysis.rst:402
msgid ""
"non-ASCII characters. Valid names may only contain \"letter-like\" and "
"\"digit-like\" characters; see :ref:`lexical-names-nonascii` for details."
msgstr ""

#: ../../reference/lexical_analysis.rst:405
msgid ""
"Names must contain at least one character, but have no upper length limit. "
"Case is significant."
msgstr ""

#: ../../reference/lexical_analysis.rst:408
msgid "Formally, names are described by the following lexical definitions:"
msgstr ""

#: ../../reference/lexical_analysis.rst:418
msgid ""
"Note that not all names matched by this grammar are valid; see :ref:`lexical-"
"names-nonascii` for details."
msgstr ""

#: ../../reference/lexical_analysis.rst:425
msgid "Keywords"
msgstr ""

#: ../../reference/lexical_analysis.rst:431
msgid ""
"The following names are used as reserved words, or *keywords* of the "
"language, and cannot be used as ordinary identifiers.  They must be spelled "
"exactly as written here:"
msgstr ""

#: ../../reference/lexical_analysis.rst:435
msgid ""
"False      await      else       import     pass\n"
"None       break      except     in         raise\n"
"True       class      finally    is         return\n"
"and        continue   for        lambda     try\n"
"as         def        from       nonlocal   while\n"
"assert     del        global     not        with\n"
"async      elif       if         or         yield"
msgstr ""

#: ../../reference/lexical_analysis.rst:449
msgid "Soft Keywords"
msgstr ""

#: ../../reference/lexical_analysis.rst:455
msgid ""
"Some names are only reserved under specific contexts. These are known as "
"*soft keywords*:"
msgstr ""

#: ../../reference/lexical_analysis.rst:458
msgid ""
"``match``, ``case``, and ``_``, when used in the :keyword:`match` statement."
msgstr ""

#: ../../reference/lexical_analysis.rst:459
msgid "``type``, when used in the :keyword:`type` statement."
msgstr ""

#: ../../reference/lexical_analysis.rst:460
msgid "``lazy``, when used before an :keyword:`import` statement."
msgstr ""

#: ../../reference/lexical_analysis.rst:462
msgid ""
"These syntactically act as keywords in their specific contexts, but this "
"distinction is done at the parser level, not when tokenizing."
msgstr ""

#: ../../reference/lexical_analysis.rst:465
msgid ""
"As soft keywords, their use in the grammar is possible while still "
"preserving compatibility with existing code that uses these names as "
"identifier names."
msgstr ""

#: ../../reference/lexical_analysis.rst:469
msgid "``type`` is now a soft keyword."
msgstr ""

#: ../../reference/lexical_analysis.rst:472
msgid "``lazy`` is now a soft keyword."
msgstr ""

#: ../../reference/lexical_analysis.rst:481
msgid "Reserved classes of identifiers"
msgstr ""

#: ../../reference/lexical_analysis.rst:483
msgid ""
"Certain classes of identifiers (besides keywords) have special meanings.  "
"These classes are identified by the patterns of leading and trailing "
"underscore characters:"
msgstr ""

#: ../../reference/lexical_analysis.rst:487
msgid "``_*``"
msgstr ""

#: ../../reference/lexical_analysis.rst:488
msgid "Not imported by ``from module import *``."
msgstr ""

#: ../../reference/lexical_analysis.rst:490
msgid "``_``"
msgstr ""

#: ../../reference/lexical_analysis.rst:491
msgid ""
"In a ``case`` pattern within a :keyword:`match` statement, ``_`` is a :ref:"
"`soft keyword <soft-keywords>` that denotes a :ref:`wildcard <wildcard-"
"patterns>`."
msgstr ""

#: ../../reference/lexical_analysis.rst:495
msgid ""
"Separately, the interactive interpreter makes the result of the last "
"evaluation available in the variable ``_``. (It is stored in the :mod:"
"`builtins` module, alongside built-in functions like ``print``.)"
msgstr ""

#: ../../reference/lexical_analysis.rst:500
msgid ""
"Elsewhere, ``_`` is a regular identifier. It is often used to name "
"\"special\" items, but it is not special to Python itself."
msgstr ""

#: ../../reference/lexical_analysis.rst:505
msgid ""
"The name ``_`` is often used in conjunction with internationalization; refer "
"to the documentation for the :mod:`gettext` module for more information on "
"this convention."
msgstr ""

#: ../../reference/lexical_analysis.rst:509
msgid "It is also commonly used for unused variables."
msgstr ""

#: ../../reference/lexical_analysis.rst:511
msgid "``__*__``"
msgstr ""

#: ../../reference/lexical_analysis.rst:512
msgid ""
"System-defined names, informally known as \"dunder\" names. These names are "
"defined by the interpreter and its implementation (including the standard "
"library). Current system names are discussed in the :ref:`specialnames` "
"section and elsewhere. More will likely be defined in future versions of "
"Python.  *Any* use of ``__*__`` names, in any context, that does not follow "
"explicitly documented use, is subject to breakage without warning."
msgstr ""

#: ../../reference/lexical_analysis.rst:519
msgid "``__*``"
msgstr ""

#: ../../reference/lexical_analysis.rst:520
msgid ""
"Class-private names.  Names in this category, when used within the context "
"of a class definition, are re-written to use a mangled form to help avoid "
"name clashes between \"private\" attributes of base and derived classes. See "
"section :ref:`atom-identifiers`."
msgstr ""

#: ../../reference/lexical_analysis.rst:529
msgid "Non-ASCII characters in names"
msgstr ""

#: ../../reference/lexical_analysis.rst:531
msgid ""
"Names that contain non-ASCII characters need additional normalization and "
"validation beyond the rules and grammar explained :ref:`above "
"<identifiers>`. For example, ``ř_1``, ``蛇``, or ``साँप``  are valid names, "
"but ``r〰2``, ``€``, or ``🐍`` are not."
msgstr ""

#: ../../reference/lexical_analysis.rst:537
msgid "This section explains the exact rules."
msgstr ""

#: ../../reference/lexical_analysis.rst:539
msgid ""
"All names are converted into the `normalization form`_ NFKC while parsing. "
"This means that, for example, some typographic variants of characters are "
"converted to their \"basic\" form. For example, ``fiⁿₐˡᵢᶻₐᵗᵢᵒₙ`` normalizes "
"to ``finalization``, so Python treats them as the same name::"
msgstr ""

#: ../../reference/lexical_analysis.rst:544
msgid ""
">>> fiⁿₐˡᵢᶻₐᵗᵢᵒₙ = 3\n"
">>> finalization\n"
"3"
msgstr ""

#: ../../reference/lexical_analysis.rst:550
msgid ""
"Normalization is done at the lexical level only. Run-time functions that "
"take names as *strings* generally do not normalize their arguments. For "
"example, the variable defined above is accessible at run time in the :func:"
"`globals` dictionary as ``globals()[\"finalization\"]`` but not ``globals()"
"[\"fiⁿₐˡᵢᶻₐᵗᵢᵒₙ\"]``."
msgstr ""

#: ../../reference/lexical_analysis.rst:557
msgid ""
"Similarly to how ASCII-only names must contain only letters, digits and the "
"underscore, and cannot start with a digit, a valid name must start with a "
"character in the \"letter-like\" set ``xid_start``, and the remaining "
"characters must be in the \"letter- and digit-like\" set ``xid_continue``."
msgstr ""

#: ../../reference/lexical_analysis.rst:563
msgid ""
"These sets are based on the *XID_Start* and *XID_Continue* sets as defined "
"by the Unicode standard annex `UAX-31`_. Python's ``xid_start`` additionally "
"includes the underscore (``_``). Note that Python does not necessarily "
"conform to `UAX-31`_."
msgstr ""

#: ../../reference/lexical_analysis.rst:568
msgid ""
"A non-normative listing of characters in the *XID_Start* and *XID_Continue* "
"sets as defined by Unicode is available in the `DerivedCoreProperties.txt`_ "
"file in the Unicode Character Database. For reference, the construction "
"rules for the ``xid_*`` sets are given below."
msgstr ""

#: ../../reference/lexical_analysis.rst:573
msgid "The set ``id_start`` is defined as the union of:"
msgstr ""

#: ../../reference/lexical_analysis.rst:575
msgid "Unicode category ``<Lu>`` - uppercase letters (includes ``A`` to ``Z``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:576
msgid "Unicode category ``<Ll>`` - lowercase letters (includes ``a`` to ``z``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:577
msgid "Unicode category ``<Lt>`` - titlecase letters"
msgstr ""

#: ../../reference/lexical_analysis.rst:578
msgid "Unicode category ``<Lm>`` - modifier letters"
msgstr ""

#: ../../reference/lexical_analysis.rst:579
msgid "Unicode category ``<Lo>`` - other letters"
msgstr ""

#: ../../reference/lexical_analysis.rst:580
msgid "Unicode category ``<Nl>`` - letter numbers"
msgstr ""

#: ../../reference/lexical_analysis.rst:581
msgid "{``\"_\"``} - the underscore"
msgstr ""

#: ../../reference/lexical_analysis.rst:582
msgid ""
"``<Other_ID_Start>`` - an explicit set of characters in `PropList.txt`_ to "
"support backwards compatibility"
msgstr ""

#: ../../reference/lexical_analysis.rst:585
msgid ""
"The set ``xid_start`` then closes this set under NFKC normalization, by "
"removing all characters whose normalization is not of the form ``id_start "
"id_continue*``."
msgstr ""

#: ../../reference/lexical_analysis.rst:589
msgid "The set ``id_continue`` is defined as the union of:"
msgstr ""

#: ../../reference/lexical_analysis.rst:591
msgid "``id_start`` (see above)"
msgstr ""

#: ../../reference/lexical_analysis.rst:592
msgid "Unicode category ``<Nd>`` - decimal numbers (includes ``0`` to ``9``)"
msgstr ""

#: ../../reference/lexical_analysis.rst:593
msgid "Unicode category ``<Pc>`` - connector punctuations"
msgstr ""

#: ../../reference/lexical_analysis.rst:594
msgid "Unicode category ``<Mn>`` - nonspacing marks"
msgstr ""

#: ../../reference/lexical_analysis.rst:595
msgid "Unicode category ``<Mc>`` - spacing combining marks"
msgstr ""

#: ../../reference/lexical_analysis.rst:596
msgid ""
"``<Other_ID_Continue>`` - another explicit set of characters in `PropList."
"txt`_ to support backwards compatibility"
msgstr ""

#: ../../reference/lexical_analysis.rst:599
msgid "Again, ``xid_continue`` closes this set under NFKC normalization."
msgstr ""

#: ../../reference/lexical_analysis.rst:601
msgid ""
"Unicode categories use the version of the Unicode Character Database as "
"included in the :mod:`unicodedata` module."
msgstr ""

#: ../../reference/lexical_analysis.rst:611
msgid ":pep:`3131` -- Supporting Non-ASCII Identifiers"
msgstr ""

#: ../../reference/lexical_analysis.rst:612
msgid ":pep:`672` -- Unicode-related Security Considerations for Python"
msgstr ""

#: ../../reference/lexical_analysis.rst:618
msgid "Literals"
msgstr "Literale"

#: ../../reference/lexical_analysis.rst:622
msgid "Literals are notations for constant values of some built-in types."
msgstr ""

#: ../../reference/lexical_analysis.rst:624
msgid ""
"In terms of lexical analysis, Python has :ref:`string, bytes <strings>` and :"
"ref:`numeric <numbers>` literals."
msgstr ""

#: ../../reference/lexical_analysis.rst:627
msgid ""
"Other \"literals\" are lexically denoted using :ref:`keywords <keywords>` "
"(``None``, ``True``, ``False``) and the special :ref:`ellipsis token "
"<lexical-ellipsis>` (``...``)."
msgstr ""

#: ../../reference/lexical_analysis.rst:638
msgid "String and Bytes literals"
msgstr ""

#: ../../reference/lexical_analysis.rst:640
msgid ""
"String literals are text enclosed in single quotes (``'``) or double quotes "
"(``\"``). For example:"
msgstr ""

#: ../../reference/lexical_analysis.rst:643
msgid ""
"\"spam\"\n"
"'eggs'"
msgstr ""

#: ../../reference/lexical_analysis.rst:648
msgid ""
"The quote used to start the literal also terminates it, so a string literal "
"can only contain the other quote (except with escape sequences, see below). "
"For example:"
msgstr ""

#: ../../reference/lexical_analysis.rst:652
msgid ""
"'Say \"Hello\", please.'\n"
"\"Don't do that!\""
msgstr ""

#: ../../reference/lexical_analysis.rst:657
msgid ""
"Except for this limitation, the choice of quote character (``'`` or ``\"``) "
"does not affect how the literal is parsed."
msgstr ""

#: ../../reference/lexical_analysis.rst:660
msgid ""
"Inside a string literal, the backslash (``\\``) character introduces an :dfn:"
"`escape sequence`, which has special meaning depending on the character "
"after the backslash. For example, ``\\\"`` denotes the double quote "
"character, and does *not* end the string:"
msgstr ""

#: ../../reference/lexical_analysis.rst:666
msgid ""
">>> print(\"Say \\\"Hello\\\" to everyone!\")\n"
"Say \"Hello\" to everyone!"
msgstr ""

#: ../../reference/lexical_analysis.rst:671
msgid ""
"See :ref:`escape sequences <escape-sequences>` below for a full list of such "
"sequences, and more details."
msgstr ""

#: ../../reference/lexical_analysis.rst:680
msgid "Triple-quoted strings"
msgstr ""

#: ../../reference/lexical_analysis.rst:682
msgid ""
"Strings can also be enclosed in matching groups of three single or double "
"quotes. These are generally referred to as :dfn:`triple-quoted strings`::"
msgstr ""

#: ../../reference/lexical_analysis.rst:686
msgid "\"\"\"This is a triple-quoted string.\"\"\""
msgstr ""

#: ../../reference/lexical_analysis.rst:688
msgid ""
"In triple-quoted literals, unescaped quotes are allowed (and are retained), "
"except that three unescaped quotes in a row terminate the literal, if they "
"are of the same kind (``'`` or ``\"``) used at the start::"
msgstr ""

#: ../../reference/lexical_analysis.rst:692