Update NEWS, docs, and patchlevel for 3.7.0b1

This commit is contained in:
Ned Deily
2018-01-30 18:48:26 -05:00
parent 1ca2ffdc53
commit 6e41cd95b5
91 changed files with 1042 additions and 242 deletions

View File

@@ -19,11 +19,11 @@
#define PY_MAJOR_VERSION 3
#define PY_MINOR_VERSION 7
#define PY_MICRO_VERSION 0
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_ALPHA
#define PY_RELEASE_SERIAL 4
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_BETA
#define PY_RELEASE_SERIAL 1
/* Version as a string */
#define PY_VERSION "3.7.0a4+"
#define PY_VERSION "3.7.0b1"
/*--end constants--*/
/* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.

View File

@@ -1,5 +1,5 @@
# -*- coding: utf-8 -*-
# Autogenerated by Sphinx on Mon Jan 8 21:23:03 2018
# Autogenerated by Sphinx on Tue Jan 30 18:36:07 2018
topics = {'assert': 'The "assert" statement\n'
'**********************\n'
'\n'
@@ -629,6 +629,18 @@ topics = {'assert': 'The "assert" statement\n'
'dictionary) is\n'
' unaffected.\n'
'\n'
'Changed in version 3.5: "__class__" module attribute is '
'now writable.\n'
'\n'
'New in version 3.7: "__getattr__" and "__dir__" module '
'attributes.\n'
'\n'
'See also:\n'
'\n'
' **PEP 562** - Module __getattr__ and __dir__\n'
' Describes the "__getattr__" and "__dir__" functions '
'on modules.\n'
'\n'
'\n'
'Implementing Descriptors\n'
'========================\n'
@@ -2512,17 +2524,23 @@ topics = {'assert': 'The "assert" statement\n'
'have\n'
'"return" annotation of the form ""-> expression"" after the '
'parameter\n'
'list. These annotations can be any valid Python expression and '
'are\n'
'evaluated when the function definition is executed. Annotations '
'may\n'
'be evaluated in a different order than they appear in the source '
'code.\n'
'The presence of annotations does not change the semantics of a\n'
'function. The annotation values are available as values of a\n'
"dictionary keyed by the parameters' names in the "
'"__annotations__"\n'
'attribute of the function object.\n'
'list. These annotations can be any valid Python expression. '
'The\n'
'presence of annotations does not change the semantics of a '
'function.\n'
'The annotation values are available as values of a dictionary '
'keyed by\n'
'the parameters\' names in the "__annotations__" attribute of '
'the\n'
'function object. If the "annotations" import from "__future__" '
'is\n'
'used, annotations are preserved as strings at runtime which '
'enables\n'
'postponed evaluation. Otherwise, they are evaluated when the '
'function\n'
'definition is executed. In this case annotations may be '
'evaluated in\n'
'a different order than they appear in the source code.\n'
'\n'
'It is also possible to create anonymous functions (functions not '
'bound\n'
@@ -2554,6 +2572,21 @@ topics = {'assert': 'The "assert" statement\n'
' **PEP 3107** - Function Annotations\n'
' The original specification for function annotations.\n'
'\n'
' **PEP 484** - Type Hints\n'
' Definition of a standard meaning for annotations: type '
'hints.\n'
'\n'
' **PEP 526** - Syntax for Variable Annotations\n'
' Ability to type hint variable declarations, including '
'class\n'
' variables and instance variables\n'
'\n'
' **PEP 563** - Postponed Evaluation of Annotations\n'
' Support for forward references within annotations by '
'preserving\n'
' annotations in a string form at runtime instead of eager\n'
' evaluation.\n'
'\n'
'\n'
'Class definitions\n'
'=================\n'
@@ -3748,33 +3781,30 @@ topics = {'assert': 'The "assert" statement\n'
' (com) end\n'
' (Pdb)\n'
'\n'
' To remove all commands from a breakpoint, type commands and '
'follow\n'
' it immediately with "end"; that is, give no commands.\n'
' To remove all commands from a breakpoint, type "commands" '
'and\n'
' follow it immediately with "end"; that is, give no commands.\n'
'\n'
' With no *bpnumber* argument, commands refers to the last '
'breakpoint\n'
' set.\n'
' With no *bpnumber* argument, "commands" refers to the last\n'
' breakpoint set.\n'
'\n'
' You can use breakpoint commands to start your program up '
'again.\n'
' Simply use the continue command, or step, or any other '
'command that\n'
' resumes execution.\n'
' Simply use the "continue" command, or "step", or any other '
'command\n'
' that resumes execution.\n'
'\n'
' Specifying any command resuming execution (currently '
'continue,\n'
' step, next, return, jump, quit and their abbreviations) '
'terminates\n'
' the command list (as if that command was immediately followed '
'by\n'
' end). This is because any time you resume execution (even '
'with a\n'
' simple next or step), you may encounter another '
'breakpoint—which\n'
' could have its own command list, leading to ambiguities about '
'which\n'
' list to execute.\n'
'"continue",\n'
' "step", "next", "return", "jump", "quit" and their '
'abbreviations)\n'
' terminates the command "list" (as if that command was '
'immediately\n'
' followed by end). This is because any time you resume '
'execution\n'
' (even with a simple next or step), you may encounter another\n'
' breakpoint—which could have its own command list, leading to\n'
' ambiguities about which list to execute.\n'
'\n'
" If you use the 'silent' command in the command list, the "
'usual\n'
@@ -5506,17 +5536,23 @@ topics = {'assert': 'The "assert" statement\n'
'have\n'
'"return" annotation of the form ""-> expression"" after the '
'parameter\n'
'list. These annotations can be any valid Python expression and '
'are\n'
'evaluated when the function definition is executed. Annotations '
'may\n'
'be evaluated in a different order than they appear in the source '
'code.\n'
'The presence of annotations does not change the semantics of a\n'
'function. The annotation values are available as values of a\n'
"dictionary keyed by the parameters' names in the "
'"__annotations__"\n'
'attribute of the function object.\n'
'list. These annotations can be any valid Python expression. '
'The\n'
'presence of annotations does not change the semantics of a '
'function.\n'
'The annotation values are available as values of a dictionary '
'keyed by\n'
'the parameters\' names in the "__annotations__" attribute of '
'the\n'
'function object. If the "annotations" import from "__future__" '
'is\n'
'used, annotations are preserved as strings at runtime which '
'enables\n'
'postponed evaluation. Otherwise, they are evaluated when the '
'function\n'
'definition is executed. In this case annotations may be '
'evaluated in\n'
'a different order than they appear in the source code.\n'
'\n'
'It is also possible to create anonymous functions (functions not '
'bound\n'
@@ -5546,7 +5582,22 @@ topics = {'assert': 'The "assert" statement\n'
'See also:\n'
'\n'
' **PEP 3107** - Function Annotations\n'
' The original specification for function annotations.\n',
' The original specification for function annotations.\n'
'\n'
' **PEP 484** - Type Hints\n'
' Definition of a standard meaning for annotations: type '
'hints.\n'
'\n'
' **PEP 526** - Syntax for Variable Annotations\n'
' Ability to type hint variable declarations, including '
'class\n'
' variables and instance variables\n'
'\n'
' **PEP 563** - Postponed Evaluation of Annotations\n'
' Support for forward references within annotations by '
'preserving\n'
' annotations in a string form at runtime instead of eager\n'
' evaluation.\n',
'global': 'The "global" statement\n'
'**********************\n'
'\n'
@@ -6019,11 +6070,16 @@ topics = {'assert': 'The "assert" statement\n'
'\n'
'* other future statements.\n'
'\n'
'The features recognized by Python 3.0 are "absolute_import",\n'
'"division", "generators", "unicode_literals", "print_function",\n'
'"nested_scopes" and "with_statement". They are all redundant '
'because\n'
'they are always enabled, and only kept for backwards '
'The only feature in Python 3.7 that requires using the future\n'
'statement is "annotations".\n'
'\n'
'All historical features enabled by the future statement are still\n'
'recognized by Python 3. The list includes "absolute_import",\n'
'"division", "generators", "generator_stop", "unicode_literals",\n'
'"print_function", "nested_scopes" and "with_statement". They are '
'all\n'
'redundant because they are always enabled, and only kept for '
'backwards\n'
'compatibility.\n'
'\n'
'A future statement is recognized and treated specially at compile\n'
@@ -8146,6 +8202,18 @@ topics = {'assert': 'The "assert" statement\n'
'dictionary) is\n'
' unaffected.\n'
'\n'
'Changed in version 3.5: "__class__" module attribute is now '
'writable.\n'
'\n'
'New in version 3.7: "__getattr__" and "__dir__" module '
'attributes.\n'
'\n'
'See also:\n'
'\n'
' **PEP 562** - Module __getattr__ and __dir__\n'
' Describes the "__getattr__" and "__dir__" functions on '
'modules.\n'
'\n'
'\n'
'Implementing Descriptors\n'
'------------------------\n'
@@ -9547,6 +9615,27 @@ topics = {'assert': 'The "assert" statement\n'
' formatting options that can be specified in format '
'strings.\n'
'\n'
' Note: When formatting a number ("int", "float", "float" '
'and\n'
' subclasses) with the "n" type (ex: '
'"\'{:n}\'.format(1234)"), the\n'
' function sets temporarily the "LC_CTYPE" locale to '
'the\n'
' "LC_NUMERIC" locale to decode "decimal_point" and '
'"thousands_sep"\n'
' fields of "localeconv()" if they are non-ASCII or '
'longer than 1\n'
' byte, and the "LC_NUMERIC" locale is different than '
'the\n'
' "LC_CTYPE" locale. This temporary change affects '
'other threads.\n'
'\n'
' Changed in version 3.7: When formatting a number with '
'the "n" type,\n'
' the function sets temporarily the "LC_CTYPE" locale to '
'the\n'
' "LC_NUMERIC" locale in some cases.\n'
'\n'
'str.format_map(mapping)\n'
'\n'
' Similar to "str.format(**mapping)", except that '
@@ -9598,6 +9687,16 @@ topics = {'assert': 'The "assert" statement\n'
'Unicode\n'
' Standard.\n'
'\n'
'str.isascii()\n'
'\n'
' Return true if the string is empty or all characters in '
'the string\n'
' are ASCII, false otherwise. ASCII characters have code '
'points in\n'
' the range U+0000-U+007F.\n'
'\n'
' New in version 3.7.\n'
'\n'
'str.isdecimal()\n'
'\n'
' Return true if all characters in the string are decimal '

888
Misc/NEWS.d/3.7.0b1.rst Normal file

File diff suppressed because it is too large Load Diff

View File

@@ -1,2 +0,0 @@
If the :envvar:`SOURCE_DATE_EPOCH` environment variable is set,
:mod:`py_compile` will always create hash-based ``.pyc`` files.

View File

@@ -1 +0,0 @@
Drop support of FreeBSD 9 and older.

View File

@@ -1,3 +0,0 @@
Use autoconf to detect OpenSSL libs, headers and supported features. The
ax_check_openssl M4 macro uses pkg-config to locate OpenSSL and falls back
to manual search.

View File

@@ -1,2 +0,0 @@
Fix segfault of the crypt module when libxcrypt is provided instead of
libcrypt at the system.

View File

@@ -1,2 +0,0 @@
Add C API access to the ``datetime.timezone`` constructor and
``datetime.timzone.UTC`` singleton.

View File

@@ -1,2 +0,0 @@
Fix uninitialized variable 'res' in the C implementation of os.dup2. Patch
by Stéphane Wirtel

View File

@@ -1 +0,0 @@
Get rid of recursion in the compiler for normal control flow.

View File

@@ -1 +0,0 @@
Make dict.copy() up to 5.5 times faster.

View File

@@ -1,3 +0,0 @@
Add a new contextmanager to the gc module that temporarily disables the GC
and restores the previous state. The implementation is done in C to assure
atomicity and speed.

View File

@@ -1,3 +0,0 @@
Leading whitespace is now correctly ignored when generating suggestions
for converting Py2 print statements to Py3 builtin print function calls.
Patch by Sanyam Khurana.

View File

@@ -1,3 +0,0 @@
Py_Initialize() now creates the GIL. The GIL is no longer created "on demand"
to fix a race condition when PyGILState_Ensure() is called in a non-Python
thread.

View File

@@ -1,3 +0,0 @@
``repr()`` on a dict containing its own ``values()`` or ``items()`` no
longer raises ``RecursionError``; OrderedDict similarly. Instead, use
``...``, as for other recursive structures. Patch by Ben North.

View File

@@ -1 +0,0 @@
Fixed estimation of the code stack size.

View File

@@ -1 +0,0 @@
Expose posix_spawn as a low level API in the os module.

View File

@@ -1 +0,0 @@
Remove the STORE_ANNOTATION bytecode.

View File

@@ -1,2 +0,0 @@
Improved frozenset() hash to create more distinct hash values when faced
with datasets containing many similar values.

Some files were not shown because too many files have changed in this diff Show More