From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Date: Thu, 14 Aug 2025 12:19:05 +0000 (+0300)
Subject: Python 3.14.0rc2
X-Git-Tag: v3.14.0rc2^0
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=31967d8de3d27889dd1819b8dccc2bdc17c030c1;p=thirdparty%2FPython%2Fcpython.git

Python 3.14.0rc2
---

diff --git a/Include/patchlevel.h b/Include/patchlevel.h
index 4ce274449460..121b17c205d5 100644
--- a/Include/patchlevel.h
+++ b/Include/patchlevel.h
@@ -21,10 +21,10 @@
 #define PY_MINOR_VERSION        14
 #define PY_MICRO_VERSION        0
 #define PY_RELEASE_LEVEL        PY_RELEASE_LEVEL_GAMMA
-#define PY_RELEASE_SERIAL       1
+#define PY_RELEASE_SERIAL       2
 
 /* Version as a string */
-#define PY_VERSION              "3.14.0rc1+"
+#define PY_VERSION              "3.14.0rc2"
 /*--end constants--*/
 
 
diff --git a/Lib/pydoc_data/topics.py b/Lib/pydoc_data/topics.py
index 71b1917de1c3..a0b00eae2614 100644
--- a/Lib/pydoc_data/topics.py
+++ b/Lib/pydoc_data/topics.py
@@ -1,4 +1,4 @@
-# Autogenerated by Sphinx on Tue Jul 22 19:42:37 2025
+# Autogenerated by Sphinx on Thu Aug 14 15:19:40 2025
 # as part of the release process.
 
 topics = {
@@ -492,18 +492,65 @@ The transformation rule is defined as follows:
 Python supports string and bytes literals and various numeric
 literals:
 
-   literal: stringliteral | bytesliteral | NUMBER
+   literal: strings | NUMBER
 
 Evaluation of a literal yields an object of the given type (string,
 bytes, integer, floating-point number, complex number) with the given
 value.  The value may be approximated in the case of floating-point
-and imaginary (complex) literals.  See section Literals for details.
+and imaginary (complex) literals. See section Literals for details.
+See section String literal concatenation for details on "strings".
 
 All literals correspond to immutable data types, and hence the
 object’s identity is less important than its value.  Multiple
 evaluations of literals with the same value (either the same
 occurrence in the program text or a different occurrence) may obtain
 the same object or a different object with the same value.
+
+
+String literal concatenation
+============================
+
+Multiple adjacent string or bytes literals (delimited by whitespace),
+possibly using different quoting conventions, are allowed, and their
+meaning is the same as their concatenation:
+
+   >>> "hello" 'world'
+   "helloworld"
+
+Formally:
+
+   strings: ( STRING | fstring)+ | tstring+
+
+This feature is defined at the syntactical level, so it only works
+with literals. To concatenate string expressions at run time, the ‘+’
+operator may be used:
+
+   >>> greeting = "Hello"
+   >>> space = " "
+   >>> name = "Blaise"
+   >>> print(greeting + space + name)   # not: print(greeting space name)
+   Hello Blaise
+
+Literal concatenation can freely mix raw strings, triple-quoted
+strings, and formatted string literals. For example:
+
+   >>> "Hello" r', ' f"{name}!"
+   "Hello, Blaise!"
+
+This feature can be used to reduce the number of backslashes needed,
+to split long strings conveniently across long lines, or even to add
+comments to parts of strings. For example:
+
+   re.compile("[A-Za-z_]"       # letter or underscore
+              "[A-Za-z0-9_]*"   # letter, digit or underscore
+             )
+
+However, bytes literals may only be combined with other byte literals;
+not with string literals of any kind. Also, template string literals
+may only be combined with other template string literals:
+
+   >>> t"Hello" t"{name}!"
+   Template(strings=('Hello', '!'), interpolations=(...))
 ''',
     'attribute-access': r'''Customizing attribute access
 ****************************
@@ -10209,71 +10256,112 @@ str.zfill(width)
     'strings': '''String and Bytes literals
 *************************
 
-String literals are described by the following lexical definitions:
-
-   stringliteral:   [stringprefix](shortstring | longstring)
-   stringprefix:    "r" | "u" | "R" | "U" | "f" | "F" | "t" | "T"
-                    | "fr" | "Fr" | "fR" | "FR" | "rf" | "rF" | "Rf" | "RF"
-                    | "tr" | "Tr" | "tR" | "TR" | "rt" | "rT" | "Rt" | "RT"
-   shortstring:     "'" shortstringitem* "'" | '"' shortstringitem* '"'
-   longstring:      "\'\'\'" longstringitem* "\'\'\'" | '"""' longstringitem* '"""'
-   shortstringitem: shortstringchar | stringescapeseq
-   longstringitem:  longstringchar | stringescapeseq
-   shortstringchar: <any source character except "\\" or newline or the quote>
-   longstringchar:  <any source character except "\\">
-   stringescapeseq: "\\" <any source character>
-
-   bytesliteral:   bytesprefix(shortbytes | longbytes)
-   bytesprefix:    "b" | "B" | "br" | "Br" | "bR" | "BR" | "rb" | "rB" | "Rb" | "RB"
-   shortbytes:     "'" shortbytesitem* "'" | '"' shortbytesitem* '"'
-   longbytes:      "\'\'\'" longbytesitem* "\'\'\'" | '"""' longbytesitem* '"""'
-   shortbytesitem: shortbyteschar | bytesescapeseq
-   longbytesitem:  longbyteschar | bytesescapeseq
-   shortbyteschar: <any ASCII character except "\\" or newline or the quote>
-   longbyteschar:  <any ASCII character except "\\">
-   bytesescapeseq: "\\" <any ASCII character>
-
-One syntactic restriction not indicated by these productions is that
-whitespace is not allowed between the "stringprefix" or "bytesprefix"
-and the rest of the literal. The source character set is defined by
-the encoding declaration; it is UTF-8 if no encoding declaration is
-given in the source file; see section Encoding declarations.
-
-In plain English: Both types of literals can be enclosed in matching
-single quotes ("'") or double quotes (""").  They can also be enclosed
-in matching groups of three single or double quotes (these are
-generally referred to as *triple-quoted strings*). The backslash ("\\")
-character is used to give special meaning to otherwise ordinary
-characters like "n", which means ‘newline’ when escaped ("\\n"). It can
-also be used to escape characters that otherwise have a special
-meaning, such as newline, backslash itself, or the quote character.
-See escape sequences below for examples.
-
-Bytes literals are always prefixed with "'b'" or "'B'"; they produce
-an instance of the "bytes" type instead of the "str" type.  They may
-only contain ASCII characters; bytes with a numeric value of 128 or
-greater must be expressed with escapes.
+String literals are text enclosed in single quotes ("'") or double
+quotes ("""). For example:
 
-Both string and bytes literals may optionally be prefixed with a
-letter "'r'" or "'R'"; such constructs are called *raw string
-literals* and *raw bytes literals* respectively and treat backslashes
-as literal characters.  As a result, in raw string literals, "'\\U'"
-and "'\\u'" escapes are not treated specially.
+   "spam"
+   'eggs'
+
+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:
+
+   'Say "Hello", please.'
+   "Don't do that!"
+
+Except for this limitation, the choice of quote character ("'" or """)
+does not affect how the literal is parsed.
+
+Inside a string literal, the backslash ("\\") character introduces an
+*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:
+
+   >>> print("Say \\"Hello\\" to everyone!")
+   Say "Hello" to everyone!
+
+See escape sequences below for a full list of such sequences, and more
+details.
+
+
+Triple-quoted strings
+=====================
+
+Strings can also be enclosed in matching groups of three single or
+double quotes. These are generally referred to as *triple-quoted
+strings*:
+
+   """This is a triple-quoted string."""
+
+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:
+
+   """This string has "quotes" inside."""
+
+Unescaped newlines are also allowed and retained:
+
+   \'\'\'This triple-quoted string
+   continues on the next line.\'\'\'
+
+
+String prefixes
+===============
+
+String literals can have an optional *prefix* that influences how the
+content of the literal is parsed, for example:
+
+   b"data"
+   f'{result=}'
+
+The allowed prefixes are:
+
+* "b": Bytes literal
+
+* "r": Raw string
+
+* "f": Formatted string literal (“f-string”)
+
+* "t": Template string literal (“t-string”)
+
+* "u": No effect (allowed for backwards compatibility)
+
+See the linked sections for details on each type.
+
+Prefixes are case-insensitive (for example, "B" works the same as
+"b"). The "r" prefix can be combined with "f", "t" or "b", so "fr",
+"rf", "tr", "rt", "br" and "rb" are also valid prefixes.
 
 Added in version 3.3: The "'rb'" prefix of raw bytes literals has been
 added as a synonym of "'br'".Support for the unicode legacy literal
 ("u'value'") was reintroduced to simplify the maintenance of dual
 Python 2.x and 3.x codebases. See **PEP 414** for more information.
 
-A string literal with "f" or "F" in its prefix is a *formatted string
-literal*; see f-strings.  The "f" may be combined with "r", but not
-with "b" or "u", therefore raw formatted strings are possible, but
-formatted bytes literals are not.
 
-In triple-quoted literals, unescaped newlines and quotes are allowed
-(and are retained), except that three unescaped quotes in a row
-terminate the literal.  (A “quote” is the character used to open the
-literal, i.e. either "'" or """.)
+Formal grammar
+==============
+
+String literals, except “f-strings” and “t-strings”, are described by
+the following lexical definitions.
+
+These definitions use negative lookaheads ("!") to indicate that an
+ending quote ends the literal.
+
+   STRING:          [stringprefix] (stringcontent)
+   stringprefix:    <("r" | "u" | "b" | "br" | "rb"), case-insensitive>
+   stringcontent:
+      | "'" ( !"'" stringitem)* "'"
+      | '"' ( !'"' stringitem)* '"'
+      | "\'\'\'" ( !"\'\'\'" longstringitem)* "\'\'\'"
+      | '"""' ( !'"""' longstringitem)* '"""'
+   stringitem:      stringchar | stringescapeseq
+   stringchar:      <any source_character, except backslash and newline>
+   longstringitem:  stringitem | newline
+   stringescapeseq: "\\" <any source_character>
+
+Note that as in all lexical definitions, whitespace is significant. In
+particular, the prefix (if any) must be immediately followed by the
+starting quote.
 
 
 Escape sequences
@@ -10283,101 +10371,197 @@ Unless an "'r'" or "'R'" prefix is present, escape sequences in string
 and bytes literals are interpreted according to rules similar to those
 used by Standard C.  The recognized escape sequences are:
 
-+---------------------------+-----------------------------------+---------+
-| Escape Sequence           | Meaning                           | Notes   |
-|===========================|===================================|=========|
-| "\\"<newline>              | Backslash and newline ignored     | (1)     |
-+---------------------------+-----------------------------------+---------+
-| "\\\\"                      | Backslash ("\\")                   |         |
-+---------------------------+-----------------------------------+---------+
-| "\\'"                      | Single quote ("'")                |         |
-+---------------------------+-----------------------------------+---------+
-| "\\""                      | Double quote (""")                |         |
-+---------------------------+-----------------------------------+---------+
-| "\\a"                      | ASCII Bell (BEL)                  |         |
-+---------------------------+-----------------------------------+---------+
-| "\\b"                      | ASCII Backspace (BS)              |         |
-+---------------------------+-----------------------------------+---------+
-| "\\f"                      | ASCII Formfeed (FF)               |         |
-+---------------------------+-----------------------------------+---------+
-| "\\n"                      | ASCII Linefeed (LF)               |         |
-+---------------------------+-----------------------------------+---------+
-| "\\r"                      | ASCII Carriage Return (CR)        |         |
-+---------------------------+-----------------------------------+---------+
-| "\\t"                      | ASCII Horizontal Tab (TAB)        |         |
-+---------------------------+-----------------------------------+---------+
-| "\\v"                      | ASCII Vertical Tab (VT)           |         |
-+---------------------------+-----------------------------------+---------+
-| "\\*ooo*"                  | Character with octal value *ooo*  | (2,4)   |
-+---------------------------+-----------------------------------+---------+
-| "\\x*hh*"                  | Character with hex value *hh*     | (3,4)   |
-+---------------------------+-----------------------------------+---------+
-
-Escape sequences only recognized in string literals are:
-
-+---------------------------+-----------------------------------+---------+
-| Escape Sequence           | Meaning                           | Notes   |
-|===========================|===================================|=========|
-| "\\N{*name*}"              | Character named *name* in the     | (5)     |
-|                           | Unicode database                  |         |
-+---------------------------+-----------------------------------+---------+
-| "\\u*xxxx*"                | Character with 16-bit hex value   | (6)     |
-|                           | *xxxx*                            |         |
-+---------------------------+-----------------------------------+---------+
-| "\\U*xxxxxxxx*"            | Character with 32-bit hex value   | (7)     |
-|                           | *xxxxxxxx*                        |         |
-+---------------------------+-----------------------------------+---------+
++----------------------------------------------------+----------------------------------------------------+
+| Escape Sequence                                    | Meaning                                            |
+|====================================================|====================================================|
+| "\\"<newline>                                       | Ignored end of line                                |
++----------------------------------------------------+----------------------------------------------------+
+| "\\\\"                                               | Backslash                                          |
++----------------------------------------------------+----------------------------------------------------+
+| "\\'"                                               | Single quote                                       |
++----------------------------------------------------+----------------------------------------------------+
+| "\\""                                               | Double quote                                       |
++----------------------------------------------------+----------------------------------------------------+
+| "\\a"                                               | ASCII Bell (BEL)                                   |
++----------------------------------------------------+----------------------------------------------------+
+| "\\b"                                               | ASCII Backspace (BS)                               |
++----------------------------------------------------+----------------------------------------------------+
+| "\\f"                                               | ASCII Formfeed (FF)                                |
++----------------------------------------------------+----------------------------------------------------+
+| "\\n"                                               | ASCII Linefeed (LF)                                |
++----------------------------------------------------+----------------------------------------------------+
+| "\\r"                                               | ASCII Carriage Return (CR)                         |
++----------------------------------------------------+----------------------------------------------------+
+| "\\t"                                               | ASCII Horizontal Tab (TAB)                         |
++----------------------------------------------------+----------------------------------------------------+
+| "\\v"                                               | ASCII Vertical Tab (VT)                            |
++----------------------------------------------------+----------------------------------------------------+
+| "\\*ooo*"                                           | Octal character                                    |
++----------------------------------------------------+----------------------------------------------------+
+| "\\x*hh*"                                           | Hexadecimal character                              |
++----------------------------------------------------+----------------------------------------------------+
+| "\\N{*name*}"                                       | Named Unicode character                            |
++----------------------------------------------------+----------------------------------------------------+
+| "\\u*xxxx*"                                         | Hexadecimal Unicode character                      |
++----------------------------------------------------+----------------------------------------------------+
+| "\\U*xxxxxxxx*"                                     | Hexadecimal Unicode character                      |
++----------------------------------------------------+----------------------------------------------------+
+
+
+Ignored end of line
+-------------------
+
+A backslash can be added at the end of a line to ignore the newline:
+
+   >>> 'This string will not include \\
+   ... backslashes or newline characters.'
+   'This string will not include backslashes or newline characters.'
+
+The same result can be achieved using triple-quoted strings, or
+parentheses and string literal concatenation.
+
+
+Escaped characters
+------------------
+
+To include a backslash in a non-raw Python string literal, it must be
+doubled. The "\\\\" escape sequence denotes a single backslash
+character:
+
+   >>> print('C:\\\\Program Files')
+   C:\\Program Files
+
+Similarly, the "\\'" and "\\"" sequences denote the single and double
+quote character, respectively:
+
+   >>> print('\\' and \\"')
+   ' and "
+
+
+Octal character
+---------------
+
+The sequence "\\*ooo*" denotes a *character* with the octal (base 8)
+value *ooo*:
+
+   >>> '\\120'
+   'P'
+
+Up to three octal digits (0 through 7) are accepted.
+
+In a bytes literal, *character* means a *byte* with the given value.
+In a string literal, it means a Unicode character with the given
+value.
+
+Changed in version 3.11: Octal escapes with value larger than "0o377"
+(255) produce a "DeprecationWarning".
+
+Changed in version 3.12: Octal escapes with value larger than "0o377"
+(255) produce a "SyntaxWarning". In a future Python version they will
+raise a "SyntaxError".
+
+
+Hexadecimal character
+---------------------
+
+The sequence "\\x*hh*" denotes a *character* with the hex (base 16)
+value *hh*:
+
+   >>> '\\x50'
+   'P'
+
+Unlike in Standard C, exactly two hex digits are required.
+
+In a bytes literal, *character* means a *byte* with the given value.
+In a string literal, it means a Unicode character with the given
+value.
 
-Notes:
 
-1. A backslash can be added at the end of a line to ignore the
-   newline:
+Named Unicode character
+-----------------------
+
+The sequence "\\N{*name*}" denotes a Unicode character with the given
+*name*:
+
+   >>> '\\N{LATIN CAPITAL LETTER P}'
+   'P'
+   >>> '\\N{SNAKE}'
+   '🐍'
 
-      >>> 'This string will not include \\
-      ... backslashes or newline characters.'
-      'This string will not include backslashes or newline characters.'
+This sequence cannot appear in bytes literals.
 
-   The same result can be achieved using triple-quoted strings, or
-   parentheses and string literal concatenation.
+Changed in version 3.3: Support for name aliases has been added.
 
-2. As in Standard C, up to three octal digits are accepted.
 
-   Changed in version 3.11: Octal escapes with value larger than
-   "0o377" produce a "DeprecationWarning".
+Hexadecimal Unicode characters
+------------------------------
 
-   Changed in version 3.12: Octal escapes with value larger than
-   "0o377" produce a "SyntaxWarning". In a future Python version they
-   will be eventually a "SyntaxError".
+These sequences "\\u*xxxx*" and "\\U*xxxxxxxx*" denote the Unicode
+character with the given hex (base 16) value. Exactly four digits are
+required for "\\u"; exactly eight digits are required for "\\U". The
+latter can encode any Unicode character.
 
-3. Unlike in Standard C, exactly two hex digits are required.
+   >>> '\\u1234'
+   'ሴ'
+   >>> '\\U0001f40d'
+   '🐍'
 
-4. In a bytes literal, hexadecimal and octal escapes denote the byte
-   with the given value. In a string literal, these escapes denote a
-   Unicode character with the given value.
+These sequences cannot appear in bytes literals.
 
-5. Changed in version 3.3: Support for name aliases [1] has been
-   added.
 
-6. Exactly four hex digits are required.
+Unrecognized escape sequences
+-----------------------------
+
+Unlike in Standard C, all unrecognized escape sequences are left in
+the string unchanged, that is, *the backslash is left in the result*:
 
-7. Any Unicode character can be encoded this way.  Exactly eight hex
-   digits are required.
+   >>> print('\\q')
+   \\q
+   >>> list('\\q')
+   ['\\\\', 'q']
 
-Unlike Standard C, all unrecognized escape sequences are left in the
-string unchanged, i.e., *the backslash is left in the result*.  (This
-behavior is useful when debugging: if an escape sequence is mistyped,
-the resulting output is more easily recognized as broken.)  It is also
-important to note that the escape sequences only recognized in string
-literals fall into the category of unrecognized escapes for bytes
-literals.
+Note that for bytes literals, the escape sequences only recognized in
+string literals ("\\N...", "\\u...", "\\U...") fall into the category of
+unrecognized escapes.
 
 Changed in version 3.6: Unrecognized escape sequences produce a
 "DeprecationWarning".
 
 Changed in version 3.12: Unrecognized escape sequences produce a
-"SyntaxWarning". In a future Python version they will be eventually a
+"SyntaxWarning". In a future Python version they will raise a
 "SyntaxError".
 
+
+Bytes literals
+==============
+
+*Bytes literals* are always prefixed with "'b'" or "'B'"; they produce
+an instance of the "bytes" type instead of the "str" type. They may
+only contain ASCII characters; bytes with a numeric value of 128 or
+greater must be expressed with escape sequences (typically Hexadecimal
+character or Octal character):
+
+   >>> b'\\x89PNG\\r\\n\\x1a\\n'
+   b'\\x89PNG\\r\\n\\x1a\\n'
+   >>> list(b'\\x89PNG\\r\\n\\x1a\\n')
+   [137, 80, 78, 71, 13, 10, 26, 10]
+
+Similarly, a zero byte must be expressed using an escape sequence
+(typically "\\0" or "\\x00").
+
+
+Raw string literals
+===================
+
+Both string and bytes literals may optionally be prefixed with a
+letter "'r'" or "'R'"; such constructs are called *raw string
+literals* and *raw bytes literals* respectively and treat backslashes
+as literal characters. As a result, in raw string literals, escape
+sequences are not treated specially:
+
+   >>> r'\\d{4}-\\d{2}-\\d{2}'
+   '\\\\d{4}-\\\\d{2}-\\\\d{2}'
+
 Even in a raw literal, quotes can be escaped with a backslash, but the
 backslash remains in the result; for example, "r"\\""" is a valid
 string literal consisting of two characters: a backslash and a double
@@ -10387,6 +10571,201 @@ cannot end in a single backslash* (since the backslash would escape
 the following quote character).  Note also that a single backslash
 followed by a newline is interpreted as those two characters as part
 of the literal, *not* as a line continuation.
+
+
+f-strings
+=========
+
+Added in version 3.6.
+
+A *formatted string literal* or *f-string* is a string literal that is
+prefixed with "f" or "F".  These strings may contain replacement
+fields, which are expressions delimited by curly braces "{}". While
+other string literals always have a constant value, formatted strings
+are really expressions evaluated at run time.
+
+Escape sequences are decoded like in ordinary string literals (except
+when a literal is also marked as a raw string).  After decoding, the
+grammar for the contents of the string is:
+
+   f_string:          (literal_char | "{{" | "}}" | replacement_field)*
+   replacement_field: "{" f_expression ["="] ["!" conversion] [":" format_spec] "}"
+   f_expression:      (conditional_expression | "*" or_expr)
+                        ("," conditional_expression | "," "*" or_expr)* [","]
+                      | yield_expression
+   conversion:        "s" | "r" | "a"
+   format_spec:       (literal_char | replacement_field)*
+   literal_char:      <any code point except "{", "}" or NULL>
+
+The parts of the string outside curly braces are treated literally,
+except that any doubled curly braces "'{{'" or "'}}'" are replaced
+with the corresponding single curly brace.  A single opening curly
+bracket "'{'" marks a replacement field, which starts with a Python
+expression. To display both the expression text and its value after
+evaluation, (useful in debugging), an equal sign "'='" may be added
+after the expression. A conversion field, introduced by an exclamation
+point "'!'" may follow.  A format specifier may also be appended,
+introduced by a colon "':'". A replacement field ends with a closing
+curly bracket "'}'".
+
+Expressions in formatted string literals are treated like regular
+Python expressions surrounded by parentheses, with a few exceptions.
+An empty expression is not allowed, and both "lambda"  and assignment
+expressions ":=" must be surrounded by explicit parentheses. Each
+expression is evaluated in the context where the formatted string
+literal appears, in order from left to right.  Replacement expressions
+can contain newlines in both single-quoted and triple-quoted f-strings
+and they can contain comments.  Everything that comes after a "#"
+inside a replacement field is a comment (even closing braces and
+quotes). In that case, replacement fields must be closed in a
+different line.
+
+   >>> f"abc{a # This is a comment }"
+   ... + 3}"
+   'abc5'
+
+Changed in version 3.7: Prior to Python 3.7, an "await" expression and
+comprehensions containing an "async for" clause were illegal in the
+expressions in formatted string literals due to a problem with the
+implementation.
+
+Changed in version 3.12: Prior to Python 3.12, comments were not
+allowed inside f-string replacement fields.
+
+When the equal sign "'='" is provided, the output will have the
+expression text, the "'='" and the evaluated value. Spaces after the
+opening brace "'{'", within the expression and after the "'='" are all
+retained in the output. By default, the "'='" causes the "repr()" of
+the expression to be provided, unless there is a format specified.
+When a format is specified it defaults to the "str()" of the
+expression unless a conversion "'!r'" is declared.
+
+Added in version 3.8: The equal sign "'='".
+
+If a conversion is specified, the result of evaluating the expression
+is converted before formatting.  Conversion "'!s'" calls "str()" on
+the result, "'!r'" calls "repr()", and "'!a'" calls "ascii()".
+
+The result is then formatted using the "format()" protocol.  The
+format specifier is passed to the "__format__()" method of the
+expression or conversion result.  An empty string is passed when the
+format specifier is omitted.  The formatted result is then included in
+the final value of the whole string.
+
+Top-level format specifiers may include nested replacement fields.
+These nested fields may include their own conversion fields and format
+specifiers, but may not include more deeply nested replacement fields.
+The format specifier mini-language is the same as that used by the
+"str.format()" method.
+
+Formatted string literals may be concatenated, but replacement fields
+cannot be split across literals.
+
+Some examples of formatted string literals:
+
+   >>> name = "Fred"
+   >>> f"He said his name is {name!r}."
+   "He said his name is 'Fred'."
+   >>> f"He said his name is {repr(name)}."  # repr() is equivalent to !r
+   "He said his name is 'Fred'."
+   >>> width = 10
+   >>> precision = 4
+   >>> value = decimal.Decimal("12.34567")
+   >>> f"result: {value:{width}.{precision}}"  # nested fields
+   'result:      12.35'
+   >>> today = datetime(year=2017, month=1, day=27)
+   >>> f"{today:%B %d, %Y}"  # using date format specifier
+   'January 27, 2017'
+   >>> f"{today=:%B %d, %Y}" # using date format specifier and debugging
+   'today=January 27, 2017'
+   >>> number = 1024
+   >>> f"{number:#0x}"  # using integer format specifier
+   '0x400'
+   >>> foo = "bar"
+   >>> f"{ foo = }" # preserves whitespace
+   " foo = 'bar'"
+   >>> line = "The mill's closed"
+   >>> f"{line = }"
+   'line = "The mill\\'s closed"'
+   >>> f"{line = :20}"
+   "line = The mill's closed   "
+   >>> f"{line = !r:20}"
+   'line = "The mill\\'s closed" '
+
+Reusing the outer f-string quoting type inside a replacement field is
+permitted:
+
+   >>> a = dict(x=2)
+   >>> f"abc {a["x"]} def"
+   'abc 2 def'
+
+Changed in version 3.12: Prior to Python 3.12, reuse of the same
+quoting type of the outer f-string inside a replacement field was not
+possible.
+
+Backslashes are also allowed in replacement fields and are evaluated
+the same way as in any other context:
+
+   >>> a = ["a", "b", "c"]
+   >>> print(f"List a contains:\\n{"\\n".join(a)}")
+   List a contains:
+   a
+   b
+   c
+
+Changed in version 3.12: Prior to Python 3.12, backslashes were not
+permitted inside an f-string replacement field.
+
+Formatted string literals cannot be used as docstrings, even if they
+do not include expressions.
+
+   >>> def foo():
+   ...     f"Not a docstring"
+   ...
+   >>> foo.__doc__ is None
+   True
+
+See also **PEP 498** for the proposal that added formatted string
+literals, and "str.format()", which uses a related format string
+mechanism.
+
+
+t-strings
+=========
+
+Added in version 3.14.
+
+A *template string literal* or *t-string* is a string literal that is
+prefixed with "t" or "T".  These strings follow the same syntax and
+evaluation rules as formatted string literals, with the following
+differences:
+
+* Rather than evaluating to a "str" object, t-strings evaluate to a
+  "Template" object from the "string.templatelib" module.
+
+* The "format()" protocol is not used. Instead, the format specifier
+  and conversions (if any) are passed to a new "Interpolation" object
+  that is created for each evaluated expression. It is up to code that
+  processes the resulting "Template" object to decide how to handle
+  format specifiers and conversions.
+
+* Format specifiers containing nested replacement fields are evaluated
+  eagerly, prior to being passed to the "Interpolation" object. For
+  instance, an interpolation of the form "{amount:.{precision}f}" will
+  evaluate the expression "{precision}" before setting the
+  "format_spec" attribute of the resulting "Interpolation" object; if
+  "precision" is (for example) "2", the resulting format specifier
+  will be "'.2f'".
+
+* When the equal sign "'='" is provided in an interpolation
+  expression, the resulting "Template" object will have the expression
+  text along with a "'='" character placed in its "strings" attribute.
+  The "interpolations" attribute will also contain an "Interpolation"
+  instance for the expression. By default, the "conversion" attribute
+  will be set to "'r'" (that is, "repr()"), unless there is a
+  conversion explicitly specified (in which case it overrides the
+  default) or a format specifier is provided (in which case, the
+  "conversion" defaults to "None").
 ''',
     'subscriptions': r'''Subscriptions
 *************
diff --git a/Misc/NEWS.d/3.14.0rc2.rst b/Misc/NEWS.d/3.14.0rc2.rst
new file mode 100644
index 000000000000..ffa043eebbd7
--- /dev/null
+++ b/Misc/NEWS.d/3.14.0rc2.rst
@@ -0,0 +1,216 @@
+.. date: 2025-08-06-06-29-12
+.. gh-issue: 137450
+.. nonce: JZypb7
+.. release date: 2025-08-14
+.. section: macOS
+
+macOS installer shell path management improvements: separate the installer
+``Shell profile updater`` postinstall script from the ``Update Shell
+Profile.command`` to enable more robust error handling.
+
+..
+
+.. date: 2025-07-27-02-17-40
+.. gh-issue: 137134
+.. nonce: pjgITs
+.. section: macOS
+
+Update macOS installer to ship with SQLite version 3.50.4.
+
+..
+
+.. date: 2025-07-27-02-16-53
+.. gh-issue: 137134
+.. nonce: W0WpDF
+.. section: Windows
+
+Update Windows installer to ship with SQLite 3.50.4.
+
+..
+
+.. date: 2025-08-08-15-00-38
+.. gh-issue: 137426
+.. nonce: lW-Rk2
+.. section: Library
+
+Remove the code deprecation of ``importlib.abc.ResourceLoader``. It is
+documented as deprecated, but left for backwards compatibility with other
+classes in ``importlib.abc``.
+
+..
+
+.. date: 2025-07-31-10-31-56
+.. gh-issue: 137282
+.. nonce: GOCwIC
+.. section: Library
+
+Fix tab completion and :func:`dir` on :mod:`concurrent.futures`.
+
+..
+
+.. date: 2025-07-30-18-07-33
+.. gh-issue: 137257
+.. nonce: XBtzf2
+.. section: Library
+
+Bump the version of pip bundled in ensurepip to version 25.2
+
+..
+
+.. date: 2025-07-29-21-18-31
+.. gh-issue: 137226
+.. nonce: B_4lpu
+.. section: Library
+
+Fix behavior of :meth:`annotationlib.ForwardRef.evaluate` when the
+*type_params* parameter is passed and the name of a type param is also
+present in an enclosing scope.
+
+..
+
+.. date: 2025-07-25-09-21-56
+.. gh-issue: 130522
+.. nonce: Crwq68
+.. section: Library
+
+Fix unraisable :exc:`TypeError` raised during :term:`interpreter shutdown`
+in the :mod:`threading` module.
+
+..
+
+.. date: 2025-07-24-00-38-07
+.. gh-issue: 137059
+.. nonce: fr64oW
+.. section: Library
+
+Fix handling of file URLs with a Windows drive letter in the URL authority
+by :func:`urllib.request.url2pathname`. This fixes a regression in earlier
+pre-releases of Python 3.14.
+
+..
+
+.. date: 2025-07-23-00-35-29
+.. gh-issue: 130577
+.. nonce: c7EITy
+.. section: Library
+
+:mod:`tarfile` now validates archives to ensure member offsets are
+non-negative.  (Contributed by Alexander Enrique Urieles Nieto in
+:gh:`130577`.)
+
+..
+
+.. date: 2025-07-20-16-56-55
+.. gh-issue: 135228
+.. nonce: n_XIao
+.. section: Library
+
+When :mod:`dataclasses` replaces a class with a slotted dataclass, the
+original class can now be garbage collected again. Earlier changes in Python
+3.14 caused this class to always remain in existence together with the
+replacement class synthesized by :mod:`dataclasses`.
+
+..
+
+.. date: 2025-07-01-23-00-58
+.. gh-issue: 136155
+.. nonce: 4siQQO
+.. section: Documentation
+
+We are now checking for fatal errors in EPUB builds in CI.
+
+..
+
+.. date: 2025-08-06-15-39-54
+.. gh-issue: 137400
+.. nonce: xIw0zs
+.. section: Core and Builtins
+
+Fix a crash in the :term:`free threading` build when disabling profiling or
+tracing across all threads with :c:func:`PyEval_SetProfileAllThreads` or
+:c:func:`PyEval_SetTraceAllThreads` or their Python equivalents
+:func:`threading.settrace_all_threads` and
+:func:`threading.setprofile_all_threads`.
+
+..
+
+.. date: 2025-08-02-23-04-57
+.. gh-issue: 137314
+.. nonce: wjEdzD
+.. section: Core and Builtins
+
+Fixed a regression where raw f-strings incorrectly interpreted escape
+sequences in format specifications. Raw f-strings now properly preserve
+literal backslashes in format specs, matching the behavior from Python 3.11.
+For example, ``rf"{obj:\xFF}"`` now correctly produces ``'\\xFF'`` instead
+of ``'ÿ'``. Patch by Pablo Galindo.
+
+..
+
+.. date: 2025-08-02-10-27-53
+.. gh-issue: 137308
+.. nonce: at05p_
+.. section: Core and Builtins
+
+A standalone docstring in a node body is optimized as a :keyword:`pass`
+statement to ensure that the node's body is never empty. There was a
+:exc:`ValueError` in :func:`compile` otherwise.
+
+..
+
+.. date: 2025-08-01-18-54-31
+.. gh-issue: 137288
+.. nonce: FhE7ku
+.. section: Core and Builtins
+
+Fix bug where some bytecode instructions of a boolean expression are not
+associated with the correct exception handler.
+
+..
+
+.. date: 2025-07-28-19-11-34
+.. gh-issue: 134291
+.. nonce: IiB9Id
+.. section: Core and Builtins
+
+Remove some newer macOS API usage from the JIT compiler in order to restore
+compatibility with older OSX 10.15 deployment targets.
+
+..
+
+.. date: 2025-07-25-22-31-52
+.. gh-issue: 131338
+.. nonce: zJDCMp
+.. section: Core and Builtins
+
+Disable computed stack limit checks on non-glibc linux platforms to fix
+crashes on deep recursion.
+
+..
+
+.. date: 2025-07-24-17-30-58
+.. gh-issue: 136870
+.. nonce: ncx82J
+.. section: Core and Builtins
+
+Fix data races while de-instrumenting bytecode of code objects running
+concurrently in threads.
+
+..
+
+.. date: 2025-08-13-13-41-04
+.. gh-issue: 137573
+.. nonce: r6uwRf
+.. section: C API
+
+Mark ``_PyOptimizer_Optimize`` as :c:macro:`Py_NO_INLINE` to prevent stack
+overflow crashes on macOS.
+
+..
+
+.. date: 2025-08-13-12-10-12
+.. gh-issue: 132339
+.. nonce: 3Czz5y
+.. section: Build
+
+Add support for OpenSSL 3.5.
diff --git a/Misc/NEWS.d/next/Build/2025-08-13-12-10-12.gh-issue-132339.3Czz5y.rst b/Misc/NEWS.d/next/Build/2025-08-13-12-10-12.gh-issue-132339.3Czz5y.rst
deleted file mode 100644
index 493be0ca2da9..000000000000
--- a/Misc/NEWS.d/next/Build/2025-08-13-12-10-12.gh-issue-132339.3Czz5y.rst
+++ /dev/null
@@ -1 +0,0 @@
-Add support for OpenSSL 3.5.
diff --git a/Misc/NEWS.d/next/C_API/2025-08-13-13-41-04.gh-issue-137573.r6uwRf.rst b/Misc/NEWS.d/next/C_API/2025-08-13-13-41-04.gh-issue-137573.r6uwRf.rst
deleted file mode 100644
index dcf0e643dc1e..000000000000
--- a/Misc/NEWS.d/next/C_API/2025-08-13-13-41-04.gh-issue-137573.r6uwRf.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-Mark ``_PyOptimizer_Optimize`` as :c:macro:`Py_NO_INLINE` to
-prevent stack overflow crashes on macOS.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-24-17-30-58.gh-issue-136870.ncx82J.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-07-24-17-30-58.gh-issue-136870.ncx82J.rst
deleted file mode 100644
index 7552dc69169b..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-24-17-30-58.gh-issue-136870.ncx82J.rst
+++ /dev/null
@@ -1 +0,0 @@
-Fix data races while de-instrumenting bytecode of code objects running concurrently in threads.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-25-22-31-52.gh-issue-131338.zJDCMp.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-07-25-22-31-52.gh-issue-131338.zJDCMp.rst
deleted file mode 100644
index 6c064e8f4a03..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-25-22-31-52.gh-issue-131338.zJDCMp.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-Disable computed stack limit checks on non-glibc linux platforms to fix
-crashes on deep recursion.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-28-19-11-34.gh-issue-134291.IiB9Id.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-07-28-19-11-34.gh-issue-134291.IiB9Id.rst
deleted file mode 100644
index 1605bcc35741..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-07-28-19-11-34.gh-issue-134291.IiB9Id.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-Remove some newer macOS API usage from the JIT compiler in order to restore
-compatibility with older OSX 10.15 deployment targets.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-01-18-54-31.gh-issue-137288.FhE7ku.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-08-01-18-54-31.gh-issue-137288.FhE7ku.rst
deleted file mode 100644
index 37c143f18e76..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-01-18-54-31.gh-issue-137288.FhE7ku.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-Fix bug where some bytecode instructions of a boolean expression are not
-associated with the correct exception handler.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-10-27-53.gh-issue-137308.at05p_.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-10-27-53.gh-issue-137308.at05p_.rst
deleted file mode 100644
index 8003de422b29..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-10-27-53.gh-issue-137308.at05p_.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-A standalone docstring in a node body is optimized as a :keyword:`pass`
-statement to ensure that the node's body is never empty. There was a
-:exc:`ValueError` in :func:`compile` otherwise.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-23-04-57.gh-issue-137314.wjEdzD.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-23-04-57.gh-issue-137314.wjEdzD.rst
deleted file mode 100644
index 09d0c3e68fc1..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-02-23-04-57.gh-issue-137314.wjEdzD.rst
+++ /dev/null
@@ -1,5 +0,0 @@
-Fixed a regression where raw f-strings incorrectly interpreted
-escape sequences in format specifications. Raw f-strings now properly preserve
-literal backslashes in format specs, matching the behavior from Python 3.11.
-For example, ``rf"{obj:\xFF}"`` now correctly produces ``'\\xFF'`` instead of
-``'ÿ'``. Patch by Pablo Galindo.
diff --git a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-06-15-39-54.gh-issue-137400.xIw0zs.rst b/Misc/NEWS.d/next/Core_and_Builtins/2025-08-06-15-39-54.gh-issue-137400.xIw0zs.rst
deleted file mode 100644
index a464cf48948f..000000000000
--- a/Misc/NEWS.d/next/Core_and_Builtins/2025-08-06-15-39-54.gh-issue-137400.xIw0zs.rst
+++ /dev/null
@@ -1,4 +0,0 @@
-Fix a crash in the :term:`free threading` build when disabling profiling or tracing
-across all threads with :c:func:`PyEval_SetProfileAllThreads` or
-:c:func:`PyEval_SetTraceAllThreads` or their Python equivalents
-:func:`threading.settrace_all_threads` and :func:`threading.setprofile_all_threads`.
diff --git a/Misc/NEWS.d/next/Documentation/2025-07-01-23-00-58.gh-issue-136155.4siQQO.rst b/Misc/NEWS.d/next/Documentation/2025-07-01-23-00-58.gh-issue-136155.4siQQO.rst
deleted file mode 100644
index 70f54936c80f..000000000000
--- a/Misc/NEWS.d/next/Documentation/2025-07-01-23-00-58.gh-issue-136155.4siQQO.rst
+++ /dev/null
@@ -1 +0,0 @@
-We are now checking for fatal errors in EPUB builds in CI.
diff --git a/Misc/NEWS.d/next/Library/2025-07-20-16-56-55.gh-issue-135228.n_XIao.rst b/Misc/NEWS.d/next/Library/2025-07-20-16-56-55.gh-issue-135228.n_XIao.rst
deleted file mode 100644
index 517a37feb37a..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-20-16-56-55.gh-issue-135228.n_XIao.rst
+++ /dev/null
@@ -1,4 +0,0 @@
-When :mod:`dataclasses` replaces a class with a slotted dataclass, the
-original class can now be garbage collected again. Earlier changes in Python
-3.14 caused this class to always remain in existence together with the replacement
-class synthesized by :mod:`dataclasses`.
diff --git a/Misc/NEWS.d/next/Library/2025-07-23-00-35-29.gh-issue-130577.c7EITy.rst b/Misc/NEWS.d/next/Library/2025-07-23-00-35-29.gh-issue-130577.c7EITy.rst
deleted file mode 100644
index 342cabbc865d..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-23-00-35-29.gh-issue-130577.c7EITy.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-:mod:`tarfile` now validates archives to ensure member offsets are
-non-negative.  (Contributed by Alexander Enrique Urieles Nieto in
-:gh:`130577`.)
diff --git a/Misc/NEWS.d/next/Library/2025-07-24-00-38-07.gh-issue-137059.fr64oW.rst b/Misc/NEWS.d/next/Library/2025-07-24-00-38-07.gh-issue-137059.fr64oW.rst
deleted file mode 100644
index 8c63c1f1af8b..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-24-00-38-07.gh-issue-137059.fr64oW.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-Fix handling of file URLs with a Windows drive letter in the URL authority
-by :func:`urllib.request.url2pathname`. This fixes a regression in earlier
-pre-releases of Python 3.14.
diff --git a/Misc/NEWS.d/next/Library/2025-07-25-09-21-56.gh-issue-130522.Crwq68.rst b/Misc/NEWS.d/next/Library/2025-07-25-09-21-56.gh-issue-130522.Crwq68.rst
deleted file mode 100644
index 6c2246631dda..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-25-09-21-56.gh-issue-130522.Crwq68.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-Fix unraisable :exc:`TypeError` raised during :term:`interpreter shutdown`
-in the :mod:`threading` module.
diff --git a/Misc/NEWS.d/next/Library/2025-07-29-21-18-31.gh-issue-137226.B_4lpu.rst b/Misc/NEWS.d/next/Library/2025-07-29-21-18-31.gh-issue-137226.B_4lpu.rst
deleted file mode 100644
index 522943cdd376..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-29-21-18-31.gh-issue-137226.B_4lpu.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-Fix behavior of :meth:`annotationlib.ForwardRef.evaluate` when the
-*type_params* parameter is passed and the name of a type param is also
-present in an enclosing scope.
diff --git a/Misc/NEWS.d/next/Library/2025-07-30-18-07-33.gh-issue-137257.XBtzf2.rst b/Misc/NEWS.d/next/Library/2025-07-30-18-07-33.gh-issue-137257.XBtzf2.rst
deleted file mode 100644
index fad609854025..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-30-18-07-33.gh-issue-137257.XBtzf2.rst
+++ /dev/null
@@ -1 +0,0 @@
-Bump the version of pip bundled in ensurepip to version 25.2
diff --git a/Misc/NEWS.d/next/Library/2025-07-31-10-31-56.gh-issue-137282.GOCwIC.rst b/Misc/NEWS.d/next/Library/2025-07-31-10-31-56.gh-issue-137282.GOCwIC.rst
deleted file mode 100644
index 78f169ea029b..000000000000
--- a/Misc/NEWS.d/next/Library/2025-07-31-10-31-56.gh-issue-137282.GOCwIC.rst
+++ /dev/null
@@ -1 +0,0 @@
-Fix tab completion and :func:`dir` on :mod:`concurrent.futures`.
diff --git a/Misc/NEWS.d/next/Library/2025-08-08-15-00-38.gh-issue-137426.lW-Rk2.rst b/Misc/NEWS.d/next/Library/2025-08-08-15-00-38.gh-issue-137426.lW-Rk2.rst
deleted file mode 100644
index 6d05c8a3bf4e..000000000000
--- a/Misc/NEWS.d/next/Library/2025-08-08-15-00-38.gh-issue-137426.lW-Rk2.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-Remove the code deprecation of ``importlib.abc.ResourceLoader``. It is
-documented as deprecated, but left for backwards compatibility with other
-classes in ``importlib.abc``.
diff --git a/Misc/NEWS.d/next/Windows/2025-07-27-02-16-53.gh-issue-137134.W0WpDF.rst b/Misc/NEWS.d/next/Windows/2025-07-27-02-16-53.gh-issue-137134.W0WpDF.rst
deleted file mode 100644
index ddccf95b7d03..000000000000
--- a/Misc/NEWS.d/next/Windows/2025-07-27-02-16-53.gh-issue-137134.W0WpDF.rst
+++ /dev/null
@@ -1 +0,0 @@
-Update Windows installer to ship with SQLite 3.50.4.
diff --git a/Misc/NEWS.d/next/macOS/2025-07-27-02-17-40.gh-issue-137134.pjgITs.rst b/Misc/NEWS.d/next/macOS/2025-07-27-02-17-40.gh-issue-137134.pjgITs.rst
deleted file mode 100644
index 957270f5abae..000000000000
--- a/Misc/NEWS.d/next/macOS/2025-07-27-02-17-40.gh-issue-137134.pjgITs.rst
+++ /dev/null
@@ -1 +0,0 @@
-Update macOS installer to ship with SQLite version 3.50.4.
diff --git a/Misc/NEWS.d/next/macOS/2025-08-06-06-29-12.gh-issue-137450.JZypb7.rst b/Misc/NEWS.d/next/macOS/2025-08-06-06-29-12.gh-issue-137450.JZypb7.rst
deleted file mode 100644
index 5efd74660c95..000000000000
--- a/Misc/NEWS.d/next/macOS/2025-08-06-06-29-12.gh-issue-137450.JZypb7.rst
+++ /dev/null
@@ -1,3 +0,0 @@
-macOS installer shell path management improvements: separate the installer
-``Shell profile updater`` postinstall script from the
-``Update Shell Profile.command`` to enable more robust error handling.
diff --git a/README.rst b/README.rst
index 63211550bc66..864d2d338421 100644
--- a/README.rst
+++ b/README.rst
@@ -1,4 +1,4 @@
-This is Python version 3.14.0 release candidate 1
+This is Python version 3.14.0 release candidate 2
 =================================================
 
 .. image:: https://github.com/python/cpython/actions/workflows/build.yml/badge.svg?branch=main&event=push