Skip to content
Snippets Groups Projects
Unverified Commit e2b4e4ba authored by Pablo Galindo's avatar Pablo Galindo
Browse files

Python 3.11.0a2

parent 3d42cd94
No related branches found
No related tags found
No related merge requests found
Showing
with 1395 additions and 80 deletions
......@@ -20,10 +20,10 @@
#define PY_MINOR_VERSION 11
#define PY_MICRO_VERSION 0
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_ALPHA
#define PY_RELEASE_SERIAL 1
#define PY_RELEASE_SERIAL 2
/* Version as a string */
#define PY_VERSION "3.11.0a1+"
#define PY_VERSION "3.11.0a2"
/*--end constants--*/
/* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.
......
# -*- coding: utf-8 -*-
# Autogenerated by Sphinx on Tue Oct 5 13:43:52 2021
# Autogenerated by Sphinx on Fri Nov 5 19:03:45 2021
topics = {'assert': 'The "assert" statement\n'
'**********************\n'
'\n'
......@@ -3339,9 +3339,9 @@
'\n'
'The same keyword should not be repeated in class patterns.\n'
'\n'
'The following is the logical flow for matching a mapping '
'pattern\n'
'against a subject value:\n'
'The following is the logical flow for matching a class pattern '
'against\n'
'a subject value:\n'
'\n'
'1. If "name_or_attr" is not an instance of the builtin "type" , '
'raise\n'
......@@ -5579,9 +5579,9 @@
'operations.\n'
'\n'
'If the "global" statement occurs within a block, all uses of '
'the name\n'
'specified in the statement refer to the binding of that name in '
'the\n'
'the names\n'
'specified in the statement refer to the bindings of those names '
'in the\n'
'top-level namespace. Names are resolved in the top-level '
'namespace by\n'
'searching the global namespace, i.e. the namespace of the '
......@@ -5590,9 +5590,10 @@
'namespace\n'
'of the module "builtins". The global namespace is searched '
'first. If\n'
'the name is not found there, the builtins namespace is '
'searched. The\n'
'"global" statement must precede all uses of the name.\n'
'the names are not found there, the builtins namespace is '
'searched.\n'
'The "global" statement must precede all uses of the listed '
'names.\n'
'\n'
'The "global" statement has the same scope as a name binding '
'operation\n'
......@@ -6948,22 +6949,31 @@
'trailing underscore characters:\n'
'\n'
'"_*"\n'
' Not imported by "from module import *". The special '
'identifier "_"\n'
' is used in the interactive interpreter to store the result '
'of the\n'
' last evaluation; it is stored in the "builtins" module. '
'When not\n'
' in interactive mode, "_" has no special meaning and is not '
'defined.\n'
' See section The import statement.\n'
' Not imported by "from module import *".\n'
'\n'
'"_"\n'
' In a "case" pattern within a "match" statement, "_" is a '
'soft\n'
' keyword that denotes a wildcard.\n'
'\n'
' Separately, the interactive interpreter makes the result of '
'the\n'
' last evaluation available in the variable "_". (It is '
'stored in the\n'
' "builtins" module, alongside built-in functions like '
'"print".)\n'
'\n'
' Elsewhere, "_" is a regular identifier. It is often used to '
'name\n'
' “special” items, but it is not special to Python itself.\n'
'\n'
' Note:\n'
'\n'
' The name "_" is often used in conjunction with\n'
' internationalization; refer to the documentation for the\n'
' "gettext" module for more information on this '
'convention.\n'
'convention.It is\n'
' also commonly used for unused variables.\n'
'\n'
'"__*__"\n'
' System-defined names, informally known as “dunder” names. '
......@@ -7118,15 +7128,23 @@
'trailing underscore characters:\n'
'\n'
'"_*"\n'
' Not imported by "from module import *". The special '
'identifier "_"\n'
' is used in the interactive interpreter to store the result '
' Not imported by "from module import *".\n'
'\n'
'"_"\n'
' In a "case" pattern within a "match" statement, "_" is a '
'soft\n'
' keyword that denotes a wildcard.\n'
'\n'
' Separately, the interactive interpreter makes the result '
'of the\n'
' last evaluation; it is stored in the "builtins" module. '
'When not\n'
' in interactive mode, "_" has no special meaning and is not '
'defined.\n'
' See section The import statement.\n'
' last evaluation available in the variable "_". (It is '
'stored in the\n'
' "builtins" module, alongside built-in functions like '
'"print".)\n'
'\n'
' Elsewhere, "_" is a regular identifier. It is often used '
'to name\n'
' “special” items, but it is not special to Python itself.\n'
'\n'
' Note:\n'
'\n'
......@@ -7134,7 +7152,8 @@
' internationalization; refer to the documentation for '
'the\n'
' "gettext" module for more information on this '
'convention.\n'
'convention.It is\n'
' also commonly used for unused variables.\n'
'\n'
'"__*__"\n'
' System-defined names, informally known as “dunder” names. '
......@@ -7678,8 +7697,8 @@
'operations.\n'
'\n'
'If the "global" statement occurs within a block, all uses of the '
'name\n'
'specified in the statement refer to the binding of that name in '
'names\n'
'specified in the statement refer to the bindings of those names in '
'the\n'
'top-level namespace. Names are resolved in the top-level '
'namespace by\n'
......@@ -7688,9 +7707,9 @@
'namespace\n'
'of the module "builtins". The global namespace is searched '
'first. If\n'
'the name is not found there, the builtins namespace is searched. '
'The\n'
'"global" statement must precede all uses of the name.\n'
'the names are not found there, the builtins namespace is '
'searched.\n'
'The "global" statement must precede all uses of the listed names.\n'
'\n'
'The "global" statement has the same scope as a name binding '
'operation\n'
......@@ -8025,9 +8044,9 @@
' of the object truncated to an "Integral" (typically an '
'"int").\n'
'\n'
' If "__int__()" is not defined then the built-in function '
'"int()"\n'
' falls back to "__trunc__()".\n',
' The built-in function "int()" falls back to '
'"__trunc__()" if\n'
' neither "__int__()" nor "__index__()" is defined.\n',
'objects': 'Objects, values and types\n'
'*************************\n'
'\n'
......@@ -10765,9 +10784,9 @@
' of the object truncated to an "Integral" (typically an '
'"int").\n'
'\n'
' If "__int__()" is not defined then the built-in function '
'"int()"\n'
' falls back to "__trunc__()".\n'
' The built-in function "int()" falls back to "__trunc__()" '
'if\n'
' neither "__int__()" nor "__index__()" is defined.\n'
'\n'
'\n'
'With Statement Context Managers\n'
......
This diff is collapsed.
Avoid linking libpython with libcrypt.
Prevent ``internal configure error`` when running ``configure``
with recent versions of non-Apple clang. Patch by David Bohman.
Building Python now requires a C99 ``<math.h>`` header file providing
the following functions: ``copysign()``, ``hypot()``, ``isfinite()``,
``isinf()``, ``isnan()``, ``round()``.
Patch by Victor Stinner.
Fixed regression in handling of ``LDFLAGS`` and ``CPPFLAGS`` options
where :meth:`argparse.parse_known_args` could interpret an option as
one of the built-in command line argument, for example ``-h`` for help.
The ``configure`` script now checks whether OpenSSL headers and libraries
provide required APIs. Most common APIs are verified. The check detects
outdated or missing OpenSSL. Failures do not stop configure.
Update :data:`sys.version` to use ``main`` as fallback information.
Patch by Jeong YunWon.
Fill in missing entries in Modules/Setup.
``setup.py`` no longer defines ``Py_BUILD_CORE_MODULE``. Instead every
module, that uses the internal API, defines the macro.
:mod:`pyexpat` and :mod:`_elementtree` no longer define obsolete macros ``HAVE_EXPAT_CONFIG_H`` and ``USE_PYEXPAT_CAPI``. ``XML_POOR_ENTROPY`` is now defined in ``expat_config.h``.
``Modules/Setup`` now use ``PY_CFLAGS_NODIST`` instead of ``PY_CFLAGS`` to
compile shared modules.
``setup.py`` and ``makesetup`` now track build dependencies on all Python
header files and module specific header files.
The :mod:`math` and :mod:`cmath` implementation now require a C99 compatible
``libm`` and no longer ship with workarounds for missing acosh, asinh, atanh,
expm1, and log1p functions.
``Modules/Setup`` and ``Modules/makesetup`` have been improved. The
``Setup`` file now contains working rules for all extensions. Outdated
comments have been removed. Rules defined by ``makesetup`` track
dependencies correctly.
Fix warning of ``swprintf`` and ``%s`` usage in ``_testembed.c``
``setup.py`` now uses values from configure script to build the ``_uuid``
extension module. Configure now detects util-linux's ``libuuid``, too.
:c:var:`PyStructSequence_UnnamedField` is added to the Stable ABI.
Add new :c:func:`PyThreadState_EnterTracing`, and
:c:func:`PyThreadState_LeaveTracing` functions to the limited C API to suspend
and resume tracing and profiling.
Patch by Victor Stinner.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment