2022-05-07 23:40:52 -03:00
|
|
|
|
2022-09-14 11:59:23 -03:00
|
|
|
****************************
|
|
|
|
What's New In Python 3.12
|
|
|
|
****************************
|
|
|
|
|
|
|
|
:Release: |release|
|
|
|
|
:Date: |today|
|
|
|
|
|
|
|
|
.. Rules for maintenance:
|
|
|
|
|
|
|
|
* Anyone can add text to this document. Do not spend very much time
|
|
|
|
on the wording of your changes, because your text will probably
|
|
|
|
get rewritten to some degree.
|
|
|
|
|
|
|
|
* The maintainer will go through Misc/NEWS periodically and add
|
|
|
|
changes; it's therefore more important to add your changes to
|
|
|
|
Misc/NEWS than to this file.
|
|
|
|
|
|
|
|
* This is not a complete list of every single change; completeness
|
|
|
|
is the purpose of Misc/NEWS. Some changes I consider too small
|
|
|
|
or esoteric to include. If such a change is added to the text,
|
|
|
|
I'll just remove it. (This is another reason you shouldn't spend
|
|
|
|
too much time on writing your addition.)
|
|
|
|
|
|
|
|
* If you want to draw your new text to the attention of the
|
|
|
|
maintainer, add 'XXX' to the beginning of the paragraph or
|
|
|
|
section.
|
|
|
|
|
|
|
|
* It's OK to just add a fragmentary note about a change. For
|
|
|
|
example: "XXX Describe the transmogrify() function added to the
|
|
|
|
socket module." The maintainer will research the change and
|
|
|
|
write the necessary text.
|
|
|
|
|
|
|
|
* You can comment out your additions if you like, but it's not
|
|
|
|
necessary (especially when a final release is some months away).
|
|
|
|
|
|
|
|
* Credit the author of a patch or bugfix. Just the name is
|
|
|
|
sufficient; the e-mail address isn't necessary.
|
|
|
|
|
2022-10-09 19:29:25 -03:00
|
|
|
* It's helpful to add the issue number as a comment:
|
2022-09-14 11:59:23 -03:00
|
|
|
|
|
|
|
XXX Describe the transmogrify() function added to the socket
|
|
|
|
module.
|
2022-10-09 19:29:25 -03:00
|
|
|
(Contributed by P.Y. Developer in :gh:`12345`.)
|
2022-09-14 11:59:23 -03:00
|
|
|
|
2022-09-16 15:26:02 -03:00
|
|
|
This saves the maintainer the effort of going through the VCS log when
|
|
|
|
researching a change.
|
2022-09-14 11:59:23 -03:00
|
|
|
|
|
|
|
This article explains the new features in Python 3.12, compared to 3.11.
|
|
|
|
|
|
|
|
For full details, see the :ref:`changelog <changelog>`.
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
|
|
|
Prerelease users should be aware that this document is currently in draft
|
|
|
|
form. It will be updated substantially as Python 3.12 moves towards release,
|
|
|
|
so it's worth checking back even after reading earlier versions.
|
|
|
|
|
|
|
|
|
|
|
|
Summary -- Release highlights
|
|
|
|
=============================
|
|
|
|
|
|
|
|
.. This section singles out the most important changes in Python 3.12.
|
|
|
|
Brevity is key.
|
|
|
|
|
|
|
|
|
|
|
|
.. PEP-sized items next.
|
|
|
|
|
|
|
|
Important deprecations, removals or restrictions:
|
|
|
|
|
|
|
|
* :pep:`623`, Remove wstr from Unicode
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-11-03 15:27:27 -03:00
|
|
|
* :pep:`632`, Remove the ``distutils`` package.
|
|
|
|
|
2022-11-01 10:01:20 -03:00
|
|
|
Improved Error Messages
|
|
|
|
=======================
|
|
|
|
|
2022-11-07 09:37:14 -04:00
|
|
|
* Modules from the standard library are now potentially suggested as part of
|
|
|
|
the error messages displayed by the interpreter when a :exc:`NameError` is
|
|
|
|
raised to the top level. Contributed by Pablo Galindo in :gh:`98254`.
|
|
|
|
|
|
|
|
>>> sys.version_info
|
|
|
|
Traceback (most recent call last):
|
|
|
|
File "<stdin>", line 1, in <module>
|
|
|
|
NameError: name 'sys' is not defined. Did you forget to import 'sys'?
|
|
|
|
|
2022-11-06 09:52:06 -04:00
|
|
|
* Improve the error suggestion for :exc:`NameError` exceptions for instances.
|
|
|
|
Now if a :exc:`NameError` is raised in a method and the instance has an
|
|
|
|
attribute that's exactly equal to the name in the exception, the suggestion
|
|
|
|
will include ``self.<NAME>`` instead of the closest match in the method
|
|
|
|
scope. Contributed by Pablo Galindo in :gh:`99139`.
|
|
|
|
|
|
|
|
>>> class A:
|
|
|
|
... def __init__(self):
|
|
|
|
... self.blech = 1
|
|
|
|
...
|
|
|
|
... def foo(self):
|
|
|
|
... somethin = blech
|
|
|
|
|
|
|
|
>>> A().foo()
|
|
|
|
Traceback (most recent call last):
|
|
|
|
File "<stdin>", line 1
|
|
|
|
somethin = blech
|
|
|
|
^^^^^
|
|
|
|
NameError: name 'blech' is not defined. Did you mean: 'self.blech'?
|
|
|
|
|
|
|
|
|
2022-11-01 10:01:20 -03:00
|
|
|
* Improve the :exc:`SyntaxError` error message when the user types ``import x
|
|
|
|
from y`` instead of ``from y import x``. Contributed by Pablo Galindo in :gh:`98931`.
|
|
|
|
|
|
|
|
>>> import a.y.z from b.y.z
|
|
|
|
Traceback (most recent call last):
|
|
|
|
File "<stdin>", line 1
|
|
|
|
import a.y.z from b.y.z
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
SyntaxError: Did you mean to use 'from ... import ...' instead?
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-11-07 09:36:48 -04:00
|
|
|
* :exc:`ImportError` exceptions raised from failed ``from <module> import
|
|
|
|
<name>`` statements now include suggestions for the value of ``<name>`` based on the
|
|
|
|
available names in ``<module>``. Contributed by Pablo Galindo in :gh:`91058`.
|
|
|
|
|
|
|
|
>>> from collections import chainmap
|
|
|
|
Traceback (most recent call last):
|
|
|
|
File "<stdin>", line 1, in <module>
|
|
|
|
ImportError: cannot import name 'chainmap' from 'collections'. Did you mean: 'ChainMap'?
|
|
|
|
|
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
New Features
|
|
|
|
============
|
|
|
|
|
2022-10-27 10:06:48 -03:00
|
|
|
* Add :ref:`perf_profiling` through the new
|
|
|
|
environment variable :envvar:`PYTHONPERFSUPPORT`,
|
|
|
|
the new command-line option :option:`-X perf <-X>`,
|
|
|
|
as well as the new :func:`sys.activate_stack_trampoline`,
|
|
|
|
:func:`sys.deactivate_stack_trampoline`,
|
|
|
|
and :func:`sys.is_stack_trampoline_active` APIs.
|
|
|
|
(Design by Pablo Galindo. Contributed by Pablo Galindo and Christian Heimes
|
|
|
|
with contributions from Gregory P. Smith [Google] and Mark Shannon
|
|
|
|
in :gh:`96123`.)
|
2022-05-07 23:40:52 -03:00
|
|
|
|
|
|
|
|
|
|
|
Other Language Changes
|
|
|
|
======================
|
|
|
|
|
2022-06-28 06:54:58 -03:00
|
|
|
* :class:`types.MappingProxyType` instances are now hashable if the underlying
|
|
|
|
mapping is hashable.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`87995`.)
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-09-10 17:44:10 -03:00
|
|
|
* :class:`memoryview` now supports the half-float type (the "e" format code).
|
|
|
|
(Contributed by Dong-hee Na and Antoine Pitrou in :gh:`90751`.)
|
|
|
|
|
2022-09-27 19:23:42 -03:00
|
|
|
* The parser now raises :exc:`SyntaxError` when parsing source code containing
|
|
|
|
null bytes. (Contributed by Pablo Galindo in :gh:`96670`.)
|
|
|
|
|
|
|
|
* :func:`ast.parse` now raises :exc:`SyntaxError` instead of :exc:`ValueError`
|
|
|
|
when parsing source code containing null bytes. (Contributed by Pablo Galindo
|
|
|
|
in :gh:`96670`.)
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-10-08 11:57:09 -03:00
|
|
|
* The Garbage Collector now runs only on the eval breaker mechanism of the
|
2023-01-18 12:24:56 -04:00
|
|
|
Python bytecode evaluation loop instead of object allocations. The GC can
|
2022-10-08 11:57:09 -03:00
|
|
|
also run when :c:func:`PyErr_CheckSignals` is called so C extensions that
|
|
|
|
need to run for a long time without executing any Python code also have a
|
|
|
|
chance to execute the GC periodically. (Contributed by Pablo Galindo in
|
|
|
|
:gh:`97922`.)
|
|
|
|
|
2022-11-03 13:53:25 -03:00
|
|
|
* A backslash-character pair that is not a valid escape sequence now generates
|
|
|
|
a :exc:`SyntaxWarning`, instead of :exc:`DeprecationWarning`.
|
|
|
|
For example, ``re.compile("\d+\.\d+")`` now emits a :exc:`SyntaxWarning`
|
|
|
|
(``"\d"`` is an invalid escape sequence), use raw strings for regular
|
|
|
|
expression: ``re.compile(r"\d+\.\d+")``.
|
|
|
|
In a future Python version, :exc:`SyntaxError` will eventually be raised,
|
|
|
|
instead of :exc:`SyntaxWarning`.
|
|
|
|
(Contributed by Victor Stinner in :gh:`98401`.)
|
|
|
|
|
|
|
|
* Octal escapes with value larger than ``0o377`` (ex: ``"\477"``), deprecated
|
|
|
|
in Python 3.11, now produce a :exc:`SyntaxWarning`, instead of
|
|
|
|
:exc:`DeprecationWarning`.
|
|
|
|
In a future Python version they will be eventually a :exc:`SyntaxError`.
|
|
|
|
(Contributed by Victor Stinner in :gh:`98401`.)
|
|
|
|
|
2022-12-03 15:52:21 -04:00
|
|
|
* All builtin and extension callables expecting boolean parameters now accept
|
|
|
|
arguments of any type instead of just :class:`bool` and :class:`int`.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`60203`.)
|
|
|
|
|
2023-01-08 18:51:29 -04:00
|
|
|
* Variables used in the target part of comprehensions that are not stored to
|
|
|
|
can now be used in assignment expressions (``:=``).
|
|
|
|
For example, in ``[(b := 1) for a, b.prop in some_iter]``, the assignment to
|
|
|
|
``b`` is now allowed. Note that assigning to variables stored to in the target
|
|
|
|
part of comprehensions (like ``a``) is still disallowed, as per :pep:`572`.
|
|
|
|
(Contributed by Nikita Sobolev in :gh:`100581`.)
|
|
|
|
|
2023-03-08 22:39:33 -04:00
|
|
|
* :class:`slice` objects are now hashable, allowing them to be used as dict keys and
|
2023-03-31 10:54:17 -03:00
|
|
|
set items. (Contributed by Will Bradshaw and Furkan Onder in :gh:`101264`.)
|
2022-11-03 13:53:25 -03:00
|
|
|
|
2023-04-11 07:53:06 -03:00
|
|
|
* Exceptions raised in a typeobject's ``__set_name__`` method are no longer
|
|
|
|
wrapped by a :exc:`RuntimeError`. Context information is added to the
|
|
|
|
exception as a :pep:`678` note. (Contributed by Irit Katriel in :gh:`77757`.)
|
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
New Modules
|
|
|
|
===========
|
|
|
|
|
|
|
|
* None yet.
|
|
|
|
|
|
|
|
|
|
|
|
Improved Modules
|
|
|
|
================
|
|
|
|
|
2022-11-01 01:10:18 -03:00
|
|
|
array
|
|
|
|
-----
|
|
|
|
|
|
|
|
* The :class:`array.array` class now supports subscripting, making it a
|
|
|
|
:term:`generic type`. (Contributed by Jelle Zijlstra in :gh:`98658`.)
|
|
|
|
|
2022-10-08 17:52:19 -03:00
|
|
|
asyncio
|
|
|
|
-------
|
|
|
|
|
2023-04-08 22:59:08 -03:00
|
|
|
* The performance of writing to sockets in :mod:`asyncio` has been
|
|
|
|
significantly improved. ``asyncio`` now avoids unnecessary copying when
|
|
|
|
writing to sockets and uses :meth:`~socket.socket.sendmsg` if the platform
|
|
|
|
supports it. (Contributed by Kumar Aditya in :gh:`91166`.)
|
|
|
|
|
2022-10-08 17:52:19 -03:00
|
|
|
* On Linux, :mod:`asyncio` uses :class:`~asyncio.PidfdChildWatcher` by default
|
|
|
|
if :func:`os.pidfd_open` is available and functional instead of
|
|
|
|
:class:`~asyncio.ThreadedChildWatcher`.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`98024`.)
|
|
|
|
|
|
|
|
* The child watcher classes :class:`~asyncio.MultiLoopChildWatcher`,
|
2022-11-12 03:17:53 -04:00
|
|
|
:class:`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher`
|
|
|
|
and :class:`~asyncio.SafeChildWatcher` are deprecated and
|
2022-10-08 17:52:19 -03:00
|
|
|
will be removed in Python 3.14. It is recommended to not manually
|
|
|
|
configure a child watcher as the event loop now uses the best available
|
|
|
|
child watcher for each platform (:class:`~asyncio.PidfdChildWatcher`
|
|
|
|
if supported and :class:`~asyncio.ThreadedChildWatcher` otherwise).
|
|
|
|
(Contributed by Kumar Aditya in :gh:`94597`.)
|
|
|
|
|
2022-10-15 20:09:30 -03:00
|
|
|
* :func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`,
|
|
|
|
:meth:`asyncio.AbstractEventLoopPolicy.set_child_watcher` and
|
|
|
|
:meth:`asyncio.AbstractEventLoopPolicy.get_child_watcher` are deprecated
|
|
|
|
and will be removed in Python 3.14.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`94597`.)
|
|
|
|
|
2022-11-14 14:18:51 -04:00
|
|
|
* Add *loop_factory* parameter to :func:`asyncio.run` to allow specifying
|
|
|
|
a custom event loop factory.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`99388`.)
|
|
|
|
|
2022-12-22 09:38:12 -04:00
|
|
|
* Add C implementation of :func:`asyncio.current_task` for 4x-6x speedup.
|
|
|
|
(Contributed by Itamar Ostricher and Pranav Thulasiram Bhat in :gh:`100344`.)
|
|
|
|
|
2023-03-16 11:58:10 -03:00
|
|
|
* :func:`asyncio.iscoroutine` now returns ``False`` for generators as
|
|
|
|
:mod:`asyncio` does not support legacy generator-based coroutines.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`102748`.)
|
|
|
|
|
2023-03-16 22:28:43 -03:00
|
|
|
* :func:`asyncio.wait` now accepts generators yielding tasks.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`78530`.)
|
|
|
|
|
2023-04-12 21:45:52 -03:00
|
|
|
csv
|
|
|
|
---
|
|
|
|
|
|
|
|
* Add :data:`~csv.QUOTE_NOTNULL` and :data:`~csv.QUOTE_STRINGS` flags to
|
|
|
|
provide finer grained control of ``None`` and empty strings by
|
|
|
|
:class:`~csv.reader` and :class:`~csv.writer` objects.
|
|
|
|
|
2022-12-18 15:13:24 -04:00
|
|
|
inspect
|
|
|
|
-------
|
|
|
|
|
|
|
|
* Add :func:`inspect.markcoroutinefunction` to mark sync functions that return
|
2023-03-24 08:23:35 -03:00
|
|
|
a :term:`coroutine` for use with :func:`inspect.iscoroutinefunction`.
|
2022-12-18 15:13:24 -04:00
|
|
|
(Contributed Carlton Gibson in :gh:`99247`.)
|
2022-11-14 14:18:51 -04:00
|
|
|
|
2023-03-11 09:19:40 -04:00
|
|
|
* Add :func:`inspect.getasyncgenstate` and :func:`inspect.getasyncgenlocals`
|
|
|
|
for determining the current state of asynchronous generators.
|
|
|
|
(Contributed by Thomas Krennwallner in :issue:`35759`.)
|
|
|
|
|
2023-04-07 14:14:50 -03:00
|
|
|
* The performance of :func:`inspect.getattr_static` has been considerably
|
|
|
|
improved. Most calls to the function should be around 2x faster than they
|
|
|
|
were in Python 3.11. (Contributed by Alex Waygood in :gh:`103193`.)
|
|
|
|
|
2022-08-11 04:31:46 -03:00
|
|
|
pathlib
|
|
|
|
-------
|
|
|
|
|
|
|
|
* Add :meth:`~pathlib.Path.walk` for walking the directory trees and generating
|
|
|
|
all file or directory names within them, similar to :func:`os.walk`.
|
|
|
|
(Contributed by Stanislav Zmiev in :gh:`90385`.)
|
|
|
|
|
2022-10-28 20:20:14 -03:00
|
|
|
* Add *walk_up* optional parameter to :meth:`pathlib.PurePath.relative_to`
|
|
|
|
to allow the insertion of ``..`` entries in the result; this behavior is
|
|
|
|
more consistent with :func:`os.path.relpath`.
|
|
|
|
(Contributed by Domenico Ragusa in :issue:`40358`.)
|
|
|
|
|
2022-11-22 13:19:34 -04:00
|
|
|
* Add :meth:`pathlib.Path.is_junction` as a proxy to :func:`os.path.isjunction`.
|
|
|
|
(Contributed by Charles Machalow in :gh:`99547`.)
|
|
|
|
|
|
|
|
|
2022-07-01 11:33:35 -03:00
|
|
|
dis
|
|
|
|
---
|
|
|
|
|
|
|
|
* Pseudo instruction opcodes (which are used by the compiler but
|
|
|
|
do not appear in executable bytecode) are now exposed in the
|
|
|
|
:mod:`dis` module.
|
2023-03-24 08:23:35 -03:00
|
|
|
:opcode:`HAVE_ARGUMENT` is still relevant to real opcodes,
|
2022-09-10 15:14:01 -03:00
|
|
|
but it is not useful for pseudo instructions. Use the new
|
2022-07-01 11:33:35 -03:00
|
|
|
:data:`~dis.hasarg` collection instead.
|
|
|
|
(Contributed by Irit Katriel in :gh:`94216`.)
|
|
|
|
|
gh-67790: Support float-style formatting for Fraction instances (#100161)
This PR adds support for float-style formatting for `Fraction` objects: it supports the `"e"`, `"E"`, `"f"`, `"F"`, `"g"`, `"G"` and `"%"` presentation types, and all the various bells and whistles of the formatting mini-language for those presentation types. The behaviour almost exactly matches that of `float`, but the implementation works with the exact `Fraction` value and does not do an intermediate conversion to `float`, and so avoids loss of precision or issues with numbers that are outside the dynamic range of the `float` type.
Note that the `"n"` presentation type is _not_ supported. That support could be added later if people have a need for it.
There's one corner-case where the behaviour differs from that of float: for the `float` type, if explicit alignment is specified with a fill character of `'0'` and alignment type `'='`, then thousands separators (if specified) are inserted into the padding string:
```python
>>> format(3.14, '0=11,.2f')
'0,000,003.14'
```
The exact same effect can be achieved by using the `'0'` flag:
```python
>>> format(3.14, '011,.2f')
'0,000,003.14'
```
For `Fraction`, only the `'0'` flag has the above behaviour with respect to thousands separators: there's no special-casing of the particular `'0='` fill-character/alignment combination. Instead, we treat the fill character `'0'` just like any other:
```python
>>> format(Fraction('3.14'), '0=11,.2f')
'00000003.14'
>>> format(Fraction('3.14'), '011,.2f')
'0,000,003.14'
```
The `Fraction` formatter is also stricter about combining these two things: it's not permitted to use both the `'0'` flag _and_ explicit alignment, on the basis that we should refuse the temptation to guess in the face of ambiguity. `float` is less picky:
```python
>>> format(3.14, '0<011,.2f')
'3.140000000'
>>> format(Fraction('3.14'), '0<011,.2f')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/mdickinson/Repositories/python/cpython/Lib/fractions.py", line 414, in __format__
raise ValueError(
ValueError: Invalid format specifier '0<011,.2f' for object of type 'Fraction'; can't use explicit alignment when zero-padding
```
2023-01-22 14:44:49 -04:00
|
|
|
fractions
|
|
|
|
---------
|
|
|
|
|
|
|
|
* Objects of type :class:`fractions.Fraction` now support float-style
|
|
|
|
formatting. (Contributed by Mark Dickinson in :gh:`100161`.)
|
|
|
|
|
2023-01-08 15:38:24 -04:00
|
|
|
math
|
|
|
|
----
|
|
|
|
|
|
|
|
* Added :func:`math.sumprod` for computing a sum of products.
|
|
|
|
(Contributed by Raymond Hettinger in :gh:`100485`.)
|
|
|
|
|
2022-05-31 07:51:29 -03:00
|
|
|
os
|
|
|
|
--
|
|
|
|
|
|
|
|
* Add :data:`os.PIDFD_NONBLOCK` to open a file descriptor
|
|
|
|
for a process with :func:`os.pidfd_open` in non-blocking mode.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`93312`.)
|
|
|
|
|
2022-11-22 13:19:34 -04:00
|
|
|
* :class:`os.DirEntry` now includes an :meth:`os.DirEntry.is_junction`
|
|
|
|
method to check if the entry is a junction.
|
|
|
|
(Contributed by Charles Machalow in :gh:`99547`.)
|
|
|
|
|
2023-03-10 08:21:37 -04:00
|
|
|
* Add :func:`os.listdrives`, :func:`os.listvolumes` and :func:`os.listmounts`
|
|
|
|
functions on Windows for enumerating drives, volumes and mount points.
|
|
|
|
(Contributed by Steve Dower in :gh:`102519`.)
|
|
|
|
|
2023-03-16 14:27:21 -03:00
|
|
|
* :func:`os.stat` and :func:`os.lstat` are now more accurate on Windows.
|
|
|
|
The ``st_birthtime`` field will now be filled with the creation time
|
|
|
|
of the file, and ``st_ctime`` is deprecated but still contains the
|
|
|
|
creation time (but in the future will return the last metadata change,
|
|
|
|
for consistency with other platforms). ``st_dev`` may be up to 64 bits
|
|
|
|
and ``st_ino`` up to 128 bits depending on your file system, and
|
|
|
|
``st_rdev`` is always set to zero rather than incorrect values.
|
|
|
|
Both functions may be significantly faster on newer releases of
|
|
|
|
Windows. (Contributed by Steve Dower in :gh:`99726`.)
|
|
|
|
|
2023-01-26 20:28:27 -04:00
|
|
|
os.path
|
|
|
|
-------
|
|
|
|
|
|
|
|
* Add :func:`os.path.isjunction` to check if a given path is a junction.
|
|
|
|
(Contributed by Charles Machalow in :gh:`99547`.)
|
|
|
|
|
|
|
|
* Add :func:`os.path.splitroot` to split a path into a triad
|
|
|
|
``(drive, root, tail)``. (Contributed by Barney Gale in :gh:`101000`.)
|
2022-11-22 13:19:34 -04:00
|
|
|
|
2022-10-05 06:48:59 -03:00
|
|
|
shutil
|
|
|
|
------
|
|
|
|
|
|
|
|
* :func:`shutil.make_archive` now passes the *root_dir* argument to custom
|
|
|
|
archivers which support it.
|
|
|
|
In this case it no longer temporarily changes the current working directory
|
|
|
|
of the process to *root_dir* to perform archiving.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`74696`.)
|
|
|
|
|
2023-03-19 15:33:51 -03:00
|
|
|
* :func:`shutil.rmtree` now accepts a new argument *onexc* which is an
|
|
|
|
error handler like *onerror* but which expects an exception instance
|
2023-03-21 08:08:46 -03:00
|
|
|
rather than a *(typ, val, tb)* triplet. *onerror* is deprecated and
|
|
|
|
will be removed in Python 3.14.
|
2023-03-19 15:33:51 -03:00
|
|
|
(Contributed by Irit Katriel in :gh:`102828`.)
|
|
|
|
|
2023-04-04 19:24:13 -03:00
|
|
|
* :func:`shutil.which` now consults the *PATHEXT* environment variable to
|
|
|
|
find matches within *PATH* on Windows even when the given *cmd* includes
|
|
|
|
a directory component.
|
|
|
|
(Contributed by Charles Machalow in :gh:`103179`.)
|
|
|
|
|
|
|
|
:func:`shutil.which` will call ``NeedCurrentDirectoryForExePathW`` when
|
|
|
|
querying for executables on Windows to determine if the current working
|
|
|
|
directory should be prepended to the search path.
|
|
|
|
(Contributed by Charles Machalow in :gh:`103179`.)
|
|
|
|
|
|
|
|
:func:`shutil.which` will return a path matching the *cmd* with a component
|
|
|
|
from ``PATHEXT`` prior to a direct match elsewhere in the search path on
|
|
|
|
Windows.
|
|
|
|
(Contributed by Charles Machalow in :gh:`103179`.)
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-08-01 07:25:16 -03:00
|
|
|
sqlite3
|
|
|
|
-------
|
|
|
|
|
|
|
|
* Add a :ref:`command-line interface <sqlite3-cli>`.
|
|
|
|
(Contributed by Erlend E. Aasland in :gh:`77617`.)
|
|
|
|
|
2022-11-12 18:44:41 -04:00
|
|
|
* Add the :attr:`~sqlite3.Connection.autocommit` attribute
|
|
|
|
to :class:`~sqlite3.Connection`
|
|
|
|
and the *autocommit* parameter to :func:`~sqlite3.connect`
|
|
|
|
to control :pep:`249`-compliant
|
|
|
|
:ref:`transaction handling <sqlite3-transaction-control-autocommit>`.
|
|
|
|
(Contributed by Erlend E. Aasland in :gh:`83638`.)
|
|
|
|
|
2022-09-13 09:12:15 -03:00
|
|
|
threading
|
|
|
|
---------
|
|
|
|
|
|
|
|
* Add :func:`threading.settrace_all_threads` and
|
|
|
|
:func:`threading.setprofile_all_threads` that allow to set tracing and
|
|
|
|
profiling functions in all running threads in addition to the calling one.
|
|
|
|
(Contributed by Pablo Galindo in :gh:`93503`.)
|
|
|
|
|
2022-09-13 19:45:12 -03:00
|
|
|
unicodedata
|
|
|
|
-----------
|
|
|
|
|
|
|
|
* The Unicode database has been updated to version 15.0.0. (Contributed by
|
|
|
|
Benjamin Peterson in :gh:`96734`).
|
|
|
|
|
2023-04-02 19:12:51 -03:00
|
|
|
unittest
|
|
|
|
--------
|
|
|
|
|
|
|
|
Added ``--durations`` command line option, showing the N slowest test cases::
|
|
|
|
|
|
|
|
python3 -m unittest --durations=3 lib.tests.test_threading
|
|
|
|
.....
|
|
|
|
Slowest test durations
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
1.210s test_timeout (Lib.test.test_threading.BarrierTests)
|
|
|
|
1.003s test_default_timeout (Lib.test.test_threading.BarrierTests)
|
|
|
|
0.518s test_timeout (Lib.test.test_threading.EventTests)
|
|
|
|
|
|
|
|
(0.000 durations hidden. Use -v to show these durations.)
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
Ran 158 tests in 9.869s
|
|
|
|
|
|
|
|
OK (skipped=3)
|
|
|
|
|
|
|
|
(Contributed by Giampaolo Rodola in :issue:`4080`)
|
|
|
|
|
2023-01-22 02:59:31 -04:00
|
|
|
uuid
|
|
|
|
----
|
|
|
|
|
|
|
|
* Add a :ref:`command-line interface <uuid-cli>`.
|
|
|
|
(Contributed by Adam Chhina in :gh:`88597`.)
|
|
|
|
|
2022-10-04 19:37:33 -03:00
|
|
|
tempfile
|
|
|
|
--------
|
|
|
|
|
|
|
|
The :class:`tempfile.NamedTemporaryFile` function has a new optional parameter
|
|
|
|
*delete_on_close* (Contributed by Evgeny Zorin in :gh:`58451`.)
|
2022-08-01 07:25:16 -03:00
|
|
|
|
2023-04-07 18:06:37 -03:00
|
|
|
.. _whatsnew-typing-py312:
|
|
|
|
|
2023-02-27 17:16:11 -04:00
|
|
|
typing
|
|
|
|
------
|
|
|
|
|
|
|
|
* Add :func:`typing.override`, an override decorator telling to static type
|
|
|
|
checkers to verify that a method overrides some method or attribute of the
|
|
|
|
same name on a base class, as per :pep:`698`. (Contributed by Steven Troxler in
|
|
|
|
:gh:`101564`.)
|
|
|
|
|
2023-04-02 10:22:19 -03:00
|
|
|
* :func:`isinstance` checks against
|
|
|
|
:func:`runtime-checkable protocols <typing.runtime_checkable>` now use
|
|
|
|
:func:`inspect.getattr_static` rather than :func:`hasattr` to lookup whether
|
|
|
|
attributes exist. This means that descriptors and :meth:`~object.__getattr__`
|
|
|
|
methods are no longer unexpectedly evaluated during ``isinstance()`` checks
|
|
|
|
against runtime-checkable protocols. However, it may also mean that some
|
|
|
|
objects which used to be considered instances of a runtime-checkable protocol
|
|
|
|
may no longer be considered instances of that protocol on Python 3.12+, and
|
|
|
|
vice versa. Most users are unlikely to be affected by this change.
|
|
|
|
(Contributed by Alex Waygood in :gh:`102433`.)
|
|
|
|
|
2023-04-07 18:06:37 -03:00
|
|
|
* The members of a runtime-checkable protocol are now considered "frozen" at
|
|
|
|
runtime as soon as the class has been created. Monkey-patching attributes
|
|
|
|
onto a runtime-checkable protocol will still work, but will have no impact on
|
|
|
|
:func:`isinstance` checks comparing objects to the protocol. For example::
|
|
|
|
|
|
|
|
>>> from typing import Protocol, runtime_checkable
|
|
|
|
>>> @runtime_checkable
|
|
|
|
... class HasX(Protocol):
|
|
|
|
... x = 1
|
|
|
|
...
|
|
|
|
>>> class Foo: ...
|
|
|
|
...
|
|
|
|
>>> f = Foo()
|
|
|
|
>>> isinstance(f, HasX)
|
|
|
|
False
|
|
|
|
>>> f.x = 1
|
|
|
|
>>> isinstance(f, HasX)
|
|
|
|
True
|
|
|
|
>>> HasX.y = 2
|
|
|
|
>>> isinstance(f, HasX) # unchanged, even though HasX now also has a "y" attribute
|
|
|
|
True
|
|
|
|
|
|
|
|
This change was made in order to speed up ``isinstance()`` checks against
|
|
|
|
runtime-checkable protocols.
|
|
|
|
|
|
|
|
* The performance profile of :func:`isinstance` checks against
|
|
|
|
:func:`runtime-checkable protocols <typing.runtime_checkable>` has changed
|
|
|
|
significantly. Most ``isinstance()`` checks against protocols with only a few
|
|
|
|
members should be at least 2x faster than in 3.11, and some may be 20x
|
|
|
|
faster or more. However, ``isinstance()`` checks against protocols with seven
|
|
|
|
or more members may be slower than in Python 3.11. (Contributed by Alex
|
|
|
|
Waygood in :gh:`74690` and :gh:`103193`.)
|
|
|
|
|
2022-10-27 10:06:48 -03:00
|
|
|
sys
|
|
|
|
---
|
|
|
|
|
|
|
|
* Add :func:`sys.activate_stack_trampoline` and
|
|
|
|
:func:`sys.deactivate_stack_trampoline` for activating and deactivating
|
|
|
|
stack profiler trampolines,
|
|
|
|
and :func:`sys.is_stack_trampoline_active` for querying if stack profiler
|
|
|
|
trampolines are active.
|
|
|
|
(Contributed by Pablo Galindo and Christian Heimes
|
|
|
|
with contributions from Gregory P. Smith [Google] and Mark Shannon
|
|
|
|
in :gh:`96123`.)
|
|
|
|
|
2023-03-18 08:47:11 -03:00
|
|
|
* Add :data:`sys.last_exc` which holds the last unhandled exception that
|
|
|
|
was raised (for post-mortem debugging use cases). Deprecate the
|
|
|
|
three fields that have the same information in its legacy form:
|
|
|
|
:data:`sys.last_type`, :data:`sys.last_value` and :data:`sys.last_traceback`.
|
|
|
|
(Contributed by Irit Katriel in :gh:`102778`.)
|
|
|
|
|
2023-04-11 05:38:37 -03:00
|
|
|
* :func:`sys._current_exceptions` now returns a mapping from thread-id to an
|
|
|
|
exception instance, rather than to a ``(typ, exc, tb)`` tuple.
|
|
|
|
(Contributed by Irit Katriel in :gh:`103176`.)
|
|
|
|
|
2022-10-27 10:06:48 -03:00
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
Optimizations
|
|
|
|
=============
|
|
|
|
|
2022-05-12 02:48:38 -03:00
|
|
|
* Removed ``wstr`` and ``wstr_length`` members from Unicode objects.
|
|
|
|
It reduces object size by 8 or 16 bytes on 64bit platform. (:pep:`623`)
|
|
|
|
(Contributed by Inada Naoki in :gh:`92536`.)
|
2022-05-07 23:40:52 -03:00
|
|
|
|
gh-90536: Add support for the BOLT post-link binary optimizer (gh-95908)
* Add support for the BOLT post-link binary optimizer
Using [bolt](https://github.com/llvm/llvm-project/tree/main/bolt)
provides a fairly large speedup without any code or functionality
changes. It provides roughly a 1% speedup on pyperformance, and a
4% improvement on the Pyston web macrobenchmarks.
It is gated behind an `--enable-bolt` configure arg because not all
toolchains and environments are supported. It has been tested on a
Linux x86_64 toolchain, using llvm-bolt built from the LLVM 14.0.6
sources (their binary distribution of this version did not include bolt).
Compared to [a previous attempt](https://github.com/faster-cpython/ideas/issues/224),
this commit uses bolt's preferred "instrumentation" approach, as well as adds some non-PIE
flags which enable much better optimizations from bolt.
The effects of this change are a bit more dependent on CPU microarchitecture
than other changes, since it optimizes i-cache behavior which seems
to be a bit more variable between architectures. The 1%/4% numbers
were collected on an Intel Skylake CPU, and on an AMD Zen 3 CPU I
got a slightly larger speedup (2%/4%), and on a c6i.xlarge EC2 instance
I got a slightly lower speedup (1%/3%).
The low speedup on pyperformance is not entirely unexpected, because
BOLT improves i-cache behavior, and the benchmarks in the pyperformance
suite are small and tend to fit in i-cache.
This change uses the existing pgo profiling task (`python -m test --pgo`),
though I was able to measure about a 1% macrobenchmark improvement by
using the macrobenchmarks as the training task. I personally think that
both the PGO and BOLT tasks should be updated to use macrobenchmarks,
but for the sake of splitting up the work this PR uses the existing pgo task.
* Simplify the build flags
* Add a NEWS entry
* Update Makefile.pre.in
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
* Update configure.ac
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
* Add myself to ACKS
* Add docs
* Other review comments
* fix tab/space issue
* Make it more clear that --enable-bolt is experimental
* Add link to bolt's github page
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
2022-08-18 18:33:54 -03:00
|
|
|
* Added experimental support for using the BOLT binary optimizer in the build
|
|
|
|
process, which improves performance by 1-5%.
|
2023-04-04 21:10:45 -03:00
|
|
|
(Contributed by Kevin Modzelewski in :gh:`90536` and tuned by Dong-hee Na in :gh:`101525`)
|
gh-90536: Add support for the BOLT post-link binary optimizer (gh-95908)
* Add support for the BOLT post-link binary optimizer
Using [bolt](https://github.com/llvm/llvm-project/tree/main/bolt)
provides a fairly large speedup without any code or functionality
changes. It provides roughly a 1% speedup on pyperformance, and a
4% improvement on the Pyston web macrobenchmarks.
It is gated behind an `--enable-bolt` configure arg because not all
toolchains and environments are supported. It has been tested on a
Linux x86_64 toolchain, using llvm-bolt built from the LLVM 14.0.6
sources (their binary distribution of this version did not include bolt).
Compared to [a previous attempt](https://github.com/faster-cpython/ideas/issues/224),
this commit uses bolt's preferred "instrumentation" approach, as well as adds some non-PIE
flags which enable much better optimizations from bolt.
The effects of this change are a bit more dependent on CPU microarchitecture
than other changes, since it optimizes i-cache behavior which seems
to be a bit more variable between architectures. The 1%/4% numbers
were collected on an Intel Skylake CPU, and on an AMD Zen 3 CPU I
got a slightly larger speedup (2%/4%), and on a c6i.xlarge EC2 instance
I got a slightly lower speedup (1%/3%).
The low speedup on pyperformance is not entirely unexpected, because
BOLT improves i-cache behavior, and the benchmarks in the pyperformance
suite are small and tend to fit in i-cache.
This change uses the existing pgo profiling task (`python -m test --pgo`),
though I was able to measure about a 1% macrobenchmark improvement by
using the macrobenchmarks as the training task. I personally think that
both the PGO and BOLT tasks should be updated to use macrobenchmarks,
but for the sake of splitting up the work this PR uses the existing pgo task.
* Simplify the build flags
* Add a NEWS entry
* Update Makefile.pre.in
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
* Update configure.ac
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
* Add myself to ACKS
* Add docs
* Other review comments
* fix tab/space issue
* Make it more clear that --enable-bolt is experimental
* Add link to bolt's github page
Co-authored-by: Dong-hee Na <donghee.na92@gmail.com>
2022-08-18 18:33:54 -03:00
|
|
|
|
2022-10-23 19:57:30 -03:00
|
|
|
* Speed up the regular expression substitution (functions :func:`re.sub` and
|
2023-03-24 08:23:35 -03:00
|
|
|
:func:`re.subn` and corresponding :class:`!re.Pattern` methods) for
|
2022-10-23 19:57:30 -03:00
|
|
|
replacement strings containing group references by 2--3 times.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`91524`.)
|
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
|
2022-06-14 10:43:28 -03:00
|
|
|
CPython bytecode changes
|
|
|
|
========================
|
|
|
|
|
|
|
|
* Removed the :opcode:`LOAD_METHOD` instruction. It has been merged into
|
|
|
|
:opcode:`LOAD_ATTR`. :opcode:`LOAD_ATTR` will now behave like the old
|
|
|
|
:opcode:`LOAD_METHOD` instruction if the low bit of its oparg is set.
|
|
|
|
(Contributed by Ken Jin in :gh:`93429`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Removed the :opcode:`!JUMP_IF_FALSE_OR_POP` and :opcode:`!JUMP_IF_TRUE_OR_POP`
|
2023-03-22 15:10:48 -03:00
|
|
|
instructions. (Contributed by Irit Katriel in :gh:`102859`.)
|
|
|
|
|
2022-06-14 10:43:28 -03:00
|
|
|
|
2022-10-03 12:09:02 -03:00
|
|
|
Demos and Tools
|
|
|
|
===============
|
|
|
|
|
|
|
|
* Remove the ``Tools/demo/`` directory which contained old demo scripts. A copy
|
|
|
|
can be found in the `old-demos project
|
|
|
|
<https://github.com/gvanrossum/old-demos>`_.
|
|
|
|
(Contributed by Victor Stinner in :gh:`97681`.)
|
|
|
|
|
2022-10-04 05:49:00 -03:00
|
|
|
* Remove outdated example scripts of the ``Tools/scripts/`` directory.
|
|
|
|
A copy can be found in the `old-demos project
|
|
|
|
<https://github.com/gvanrossum/old-demos>`_.
|
|
|
|
(Contributed by Victor Stinner in :gh:`97669`.)
|
|
|
|
|
2022-10-03 12:09:02 -03:00
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
Deprecated
|
|
|
|
==========
|
|
|
|
|
2022-07-14 03:50:31 -03:00
|
|
|
* :class:`typing.Hashable` and :class:`typing.Sized` aliases for :class:`collections.abc.Hashable`
|
2022-07-21 21:36:53 -03:00
|
|
|
and :class:`collections.abc.Sized`. (:gh:`94309`.)
|
2022-07-14 03:50:31 -03:00
|
|
|
|
2022-07-20 16:37:59 -03:00
|
|
|
* The :mod:`sqlite3` :ref:`default adapters and converters
|
|
|
|
<sqlite3-default-converters>` are now deprecated.
|
|
|
|
Instead, use the :ref:`sqlite3-adapter-converter-recipes`
|
|
|
|
and tailor them to your needs.
|
|
|
|
(Contributed by Erlend E. Aasland in :gh:`90016`.)
|
|
|
|
|
2023-02-15 01:27:16 -04:00
|
|
|
* In :meth:`~sqlite3.Cursor.execute`, :exc:`DeprecationWarning` is now emitted
|
|
|
|
when :ref:`named placeholders <sqlite3-placeholders>` are used together with
|
|
|
|
parameters supplied as a :term:`sequence` instead of as a :class:`dict`.
|
|
|
|
Starting from Python 3.14, using named placeholders with parameters supplied
|
|
|
|
as a sequence will raise a :exc:`~sqlite3.ProgrammingError`.
|
|
|
|
(Contributed by Erlend E. Aasland in :gh:`101698`.)
|
|
|
|
|
2022-09-30 05:43:02 -03:00
|
|
|
* The 3-arg signatures (type, value, traceback) of :meth:`~coroutine.throw`,
|
|
|
|
:meth:`~generator.throw` and :meth:`~agen.athrow` are deprecated and
|
|
|
|
may be removed in a future version of Python. Use the single-arg versions
|
|
|
|
of these functions instead. (Contributed by Ofey Chan in :gh:`89874`.)
|
|
|
|
|
2022-10-05 19:00:45 -03:00
|
|
|
* :exc:`DeprecationWarning` is now raised when ``__package__`` on a
|
|
|
|
module differs from ``__spec__.parent`` (previously it was
|
|
|
|
:exc:`ImportWarning`).
|
|
|
|
(Contributed by Brett Cannon in :gh:`65961`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* The :meth:`~asyncio.get_event_loop` method of the
|
2023-01-13 08:40:29 -04:00
|
|
|
default event loop policy now emits a :exc:`DeprecationWarning` if there
|
|
|
|
is no current event loop set and it decides to create one.
|
|
|
|
(Contributed by Serhiy Storchaka and Guido van Rossum in :gh:`100160`.)
|
|
|
|
|
2023-01-22 21:16:48 -04:00
|
|
|
* The :mod:`xml.etree.ElementTree` module now emits :exc:`DeprecationWarning`
|
|
|
|
when testing the truth value of an :class:`xml.etree.ElementTree.Element`.
|
|
|
|
Before, the Python implementation emitted :exc:`FutureWarning`, and the C
|
|
|
|
implementation emitted nothing.
|
|
|
|
|
2023-01-24 05:29:22 -04:00
|
|
|
* In accordance with :pep:`699`, the ``ma_version_tag`` field in :c:type:`PyDictObject`
|
|
|
|
is deprecated for extension modules. Accessing this field will generate a compiler
|
|
|
|
warning at compile time. This field will be removed in Python 3.14.
|
|
|
|
(Contributed by Ramvikrams and Kumar Aditya in :gh:`101193`. PEP by Ken Jin.)
|
|
|
|
|
2023-03-16 14:27:21 -03:00
|
|
|
* The ``st_ctime`` fields return by :func:`os.stat` and :func:`os.lstat` on
|
|
|
|
Windows are deprecated. In a future release, they will contain the last
|
|
|
|
metadata change time, consistent with other platforms. For now, they still
|
|
|
|
contain the creation time, which is also available in the new ``st_birthtime``
|
|
|
|
field. (Contributed by Steve Dower in :gh:`99726`.)
|
|
|
|
|
2023-03-18 08:47:11 -03:00
|
|
|
* The :data:`sys.last_type`, :data:`sys.last_value` and :data:`sys.last_traceback`
|
|
|
|
fields are deprecated. Use :data:`sys.last_exc` instead.
|
|
|
|
(Contributed by Irit Katriel in :gh:`102778`.)
|
|
|
|
|
2023-03-21 08:08:46 -03:00
|
|
|
* The *onerror* argument of :func:`shutil.rmtree` is deprecated as will be removed
|
|
|
|
in Python 3.14. Use *onexc* instead. (Contributed by Irit Katriel in :gh:`102828`.)
|
2023-03-19 15:33:51 -03:00
|
|
|
|
|
|
|
|
2022-06-06 07:12:03 -03:00
|
|
|
Pending Removal in Python 3.13
|
2022-07-12 16:55:32 -03:00
|
|
|
------------------------------
|
2022-06-06 07:12:03 -03:00
|
|
|
|
|
|
|
The following modules and APIs have been deprecated in earlier Python releases,
|
|
|
|
and will be removed in Python 3.13.
|
|
|
|
|
|
|
|
Modules (see :pep:`594`):
|
|
|
|
|
|
|
|
* :mod:`aifc`
|
|
|
|
* :mod:`audioop`
|
|
|
|
* :mod:`cgi`
|
|
|
|
* :mod:`cgitb`
|
|
|
|
* :mod:`chunk`
|
|
|
|
* :mod:`crypt`
|
|
|
|
* :mod:`imghdr`
|
|
|
|
* :mod:`mailcap`
|
|
|
|
* :mod:`msilib`
|
|
|
|
* :mod:`nis`
|
|
|
|
* :mod:`nntplib`
|
|
|
|
* :mod:`ossaudiodev`
|
|
|
|
* :mod:`pipes`
|
|
|
|
* :mod:`sndhdr`
|
|
|
|
* :mod:`spwd`
|
|
|
|
* :mod:`sunau`
|
|
|
|
* :mod:`telnetlib`
|
|
|
|
* :mod:`uu`
|
|
|
|
* :mod:`xdrlib`
|
|
|
|
|
|
|
|
APIs:
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* :class:`!configparser.LegacyInterpolation` (:gh:`90765`)
|
2022-06-06 07:12:03 -03:00
|
|
|
* :func:`locale.getdefaultlocale` (:gh:`90817`)
|
2023-03-24 08:23:35 -03:00
|
|
|
* :meth:`!turtle.RawTurtle.settiltangle` (:gh:`50096`)
|
|
|
|
* :func:`!unittest.findTestCases` (:gh:`50096`)
|
|
|
|
* :func:`!unittest.makeSuite` (:gh:`50096`)
|
|
|
|
* :func:`!unittest.getTestCaseNames` (:gh:`50096`)
|
|
|
|
* :class:`!webbrowser.MacOSX` (:gh:`86421`)
|
2022-06-06 07:12:03 -03:00
|
|
|
|
2022-07-25 13:24:42 -03:00
|
|
|
Pending Removal in Python 3.14
|
2023-02-07 10:54:47 -04:00
|
|
|
------------------------------
|
2022-07-25 13:24:42 -03:00
|
|
|
|
|
|
|
* Deprecated the following :mod:`importlib.abc` classes, scheduled for removal in
|
|
|
|
Python 3.14:
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* :class:`!importlib.abc.ResourceReader`
|
|
|
|
* :class:`!importlib.abc.Traversable`
|
|
|
|
* :class:`!importlib.abc.TraversableResources`
|
2022-07-25 13:24:42 -03:00
|
|
|
|
|
|
|
Use :mod:`importlib.resources.abc` classes instead:
|
|
|
|
|
|
|
|
* :class:`importlib.resources.abc.Traversable`
|
|
|
|
* :class:`importlib.resources.abc.TraversableResources`
|
|
|
|
|
|
|
|
(Contributed by Jason R. Coombs and Hugo van Kemenade in :gh:`93963`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Creating immutable types (:data:`Py_TPFLAGS_IMMUTABLETYPE`) with mutable
|
2022-08-04 11:13:45 -03:00
|
|
|
bases using the C API.
|
|
|
|
|
2023-03-19 21:20:20 -03:00
|
|
|
* Deprecated the *isdst* parameter in :func:`email.utils.localtime`.
|
|
|
|
(Contributed by Alan Williams in :gh:`72346`.)
|
|
|
|
|
2022-10-06 19:40:22 -03:00
|
|
|
* ``__package__`` and ``__cached__`` will cease to be set or taken
|
|
|
|
into consideration by the import system (:gh:`97879`).
|
2022-10-05 19:00:45 -03:00
|
|
|
|
2023-01-22 21:16:48 -04:00
|
|
|
* Testing the truth value of an :class:`xml.etree.ElementTree.Element`
|
|
|
|
is deprecated and will raise an exception in Python 3.14.
|
|
|
|
|
2023-02-03 19:20:46 -04:00
|
|
|
* The default :mod:`multiprocessing` start method will change to a safer one on
|
|
|
|
Linux, BSDs, and other non-macOS POSIX platforms where ``'fork'`` is currently
|
|
|
|
the default (:gh:`84559`). Adding a runtime warning about this was deemed too
|
|
|
|
disruptive as the majority of code is not expected to care. Use the
|
|
|
|
:func:`~multiprocessing.get_context` or
|
|
|
|
:func:`~multiprocessing.set_start_method` APIs to explicitly specify when
|
|
|
|
your code *requires* ``'fork'``. See :ref:`multiprocessing-start-methods`.
|
2022-08-04 11:13:45 -03:00
|
|
|
|
2023-02-08 21:00:17 -04:00
|
|
|
* :mod:`pty` has two undocumented ``master_open()`` and ``slave_open()``
|
|
|
|
functions that have been deprecated since Python 2 but only gained a
|
|
|
|
proper :exc:`DeprecationWarning` in 3.12. Remove them in 3.14.
|
|
|
|
|
2023-04-03 12:35:04 -03:00
|
|
|
* Accessing ``co_lnotab`` was deprecated in :pep:`626` since 3.10
|
|
|
|
and was planned to be removed in 3.12
|
|
|
|
but it only got a proper :exc:`DeprecationWarning` in 3.12.
|
|
|
|
May be removed in 3.14.
|
|
|
|
(Contributed by Nikita Sobolev in :gh:`101866`.)
|
|
|
|
|
2023-03-21 08:08:46 -03:00
|
|
|
* The *onerror* argument of :func:`shutil.rmtree` is deprecated in 3.12,
|
|
|
|
and will be removed in 3.14.
|
|
|
|
|
2022-06-06 07:12:03 -03:00
|
|
|
Pending Removal in Future Versions
|
2022-07-12 16:55:32 -03:00
|
|
|
----------------------------------
|
2022-06-06 07:12:03 -03:00
|
|
|
|
|
|
|
The following APIs were deprecated in earlier Python versions and will be removed,
|
|
|
|
although there is currently no date scheduled for their removal.
|
|
|
|
|
|
|
|
* :class:`typing.Text` (:gh:`92332`)
|
|
|
|
|
|
|
|
* Currently Python accepts numeric literals immediately followed by keywords,
|
|
|
|
for example ``0in x``, ``1or x``, ``0if 1else 2``. It allows confusing
|
|
|
|
and ambiguous expressions like ``[0x1for x in y]`` (which can be
|
|
|
|
interpreted as ``[0x1 for x in y]`` or ``[0x1f or x in y]``).
|
|
|
|
A syntax warning is raised if the numeric literal is
|
|
|
|
immediately followed by one of keywords :keyword:`and`, :keyword:`else`,
|
|
|
|
:keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` and :keyword:`or`.
|
|
|
|
In a future release it will be changed to a syntax error. (:gh:`87999`)
|
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
|
|
|
|
Removed
|
|
|
|
=======
|
|
|
|
|
2022-11-03 15:27:27 -03:00
|
|
|
* Remove the ``distutils`` package. It was deprecated in Python 3.10 by
|
|
|
|
:pep:`632` "Deprecate distutils module". For projects still using
|
|
|
|
``distutils`` and cannot be updated to something else, the ``setuptools``
|
|
|
|
project can be installed: it still provides ``distutils``.
|
|
|
|
(Contributed by Victor Stinner in :gh:`92584`.)
|
|
|
|
|
2022-06-26 04:18:06 -03:00
|
|
|
* Removed many old deprecated :mod:`unittest` features:
|
|
|
|
|
|
|
|
- A number of :class:`~unittest.TestCase` method aliases:
|
|
|
|
|
|
|
|
============================ =============================== ===============
|
|
|
|
Deprecated alias Method Name Deprecated in
|
|
|
|
============================ =============================== ===============
|
|
|
|
``failUnless`` :meth:`.assertTrue` 3.1
|
|
|
|
``failIf`` :meth:`.assertFalse` 3.1
|
|
|
|
``failUnlessEqual`` :meth:`.assertEqual` 3.1
|
|
|
|
``failIfEqual`` :meth:`.assertNotEqual` 3.1
|
|
|
|
``failUnlessAlmostEqual`` :meth:`.assertAlmostEqual` 3.1
|
|
|
|
``failIfAlmostEqual`` :meth:`.assertNotAlmostEqual` 3.1
|
|
|
|
``failUnlessRaises`` :meth:`.assertRaises` 3.1
|
|
|
|
``assert_`` :meth:`.assertTrue` 3.2
|
|
|
|
``assertEquals`` :meth:`.assertEqual` 3.2
|
|
|
|
``assertNotEquals`` :meth:`.assertNotEqual` 3.2
|
|
|
|
``assertAlmostEquals`` :meth:`.assertAlmostEqual` 3.2
|
|
|
|
``assertNotAlmostEquals`` :meth:`.assertNotAlmostEqual` 3.2
|
|
|
|
``assertRegexpMatches`` :meth:`.assertRegex` 3.2
|
|
|
|
``assertRaisesRegexp`` :meth:`.assertRaisesRegex` 3.2
|
|
|
|
``assertNotRegexpMatches`` :meth:`.assertNotRegex` 3.5
|
|
|
|
============================ =============================== ===============
|
|
|
|
|
|
|
|
You can use https://github.com/isidentical/teyit to automatically modernise
|
|
|
|
your unit tests.
|
|
|
|
|
|
|
|
- Undocumented and broken :class:`~unittest.TestCase` method
|
|
|
|
``assertDictContainsSubset`` (deprecated in Python 3.2).
|
|
|
|
|
|
|
|
- Undocumented :meth:`TestLoader.loadTestsFromModule
|
|
|
|
<unittest.TestLoader.loadTestsFromModule>` parameter *use_load_tests*
|
|
|
|
(deprecated and ignored since Python 3.2).
|
|
|
|
|
|
|
|
- An alias of the :class:`~unittest.TextTestResult` class:
|
|
|
|
``_TextTestResult`` (deprecated in Python 3.2).
|
|
|
|
|
|
|
|
(Contributed by Serhiy Storchaka in :issue:`45162`.)
|
|
|
|
|
2022-06-21 18:31:25 -03:00
|
|
|
* Several names deprecated in the :mod:`configparser` way back in 3.2 have
|
|
|
|
been removed per :gh:`89336`:
|
|
|
|
|
|
|
|
* :class:`configparser.ParsingError` no longer has a ``filename`` attribute
|
|
|
|
or argument. Use the ``source`` attribute and argument instead.
|
|
|
|
* :mod:`configparser` no longer has a ``SafeConfigParser`` class. Use the
|
|
|
|
shorter :class:`~configparser.ConfigParser` name instead.
|
|
|
|
* :class:`configparser.ConfigParser` no longer has a ``readfp`` method.
|
|
|
|
Use :meth:`~configparser.ConfigParser.read_file` instead.
|
|
|
|
|
2022-05-16 14:52:08 -03:00
|
|
|
* The following undocumented :mod:`sqlite3` features, deprecated in Python
|
|
|
|
3.10, are now removed:
|
|
|
|
|
|
|
|
* ``sqlite3.enable_shared_cache()``
|
|
|
|
* ``sqlite3.OptimizedUnicode``
|
|
|
|
|
2022-06-16 11:00:43 -03:00
|
|
|
If a shared cache must be used, open the database in URI mode using the
|
|
|
|
``cache=shared`` query parameter.
|
|
|
|
|
|
|
|
The ``sqlite3.OptimizedUnicode`` text factory has been an alias for
|
|
|
|
:class:`str` since Python 3.3. Code that previously set the text factory to
|
|
|
|
``OptimizedUnicode`` can either use ``str`` explicitly, or rely on the
|
|
|
|
default value which is also ``str``.
|
|
|
|
|
2022-07-21 21:36:53 -03:00
|
|
|
(Contributed by Erlend E. Aasland in :gh:`92548`.)
|
2022-05-16 14:52:08 -03:00
|
|
|
|
2022-08-05 21:41:29 -03:00
|
|
|
* ``smtpd`` has been removed according to the schedule in :pep:`594`,
|
|
|
|
having been deprecated in Python 3.4.7 and 3.5.4.
|
|
|
|
Use aiosmtpd_ PyPI module or any other
|
|
|
|
:mod:`asyncio`-based server instead.
|
|
|
|
(Contributed by Oleg Iarygin in :gh:`93243`.)
|
|
|
|
|
|
|
|
.. _aiosmtpd: https://pypi.org/project/aiosmtpd/
|
|
|
|
|
2022-11-08 11:48:58 -04:00
|
|
|
* ``asynchat`` and ``asyncore`` have been removed
|
|
|
|
according to the schedule in :pep:`594`,
|
|
|
|
having been deprecated in Python 3.6.
|
|
|
|
Use :mod:`asyncio` instead.
|
|
|
|
(Contributed by Nikita Sobolev in :gh:`96580`.)
|
|
|
|
|
2022-06-24 03:46:53 -03:00
|
|
|
* Remove ``io.OpenWrapper`` and ``_pyio.OpenWrapper``, deprecated in Python
|
|
|
|
3.10: just use :func:`open` instead. The :func:`open` (:func:`io.open`)
|
2023-03-24 08:23:35 -03:00
|
|
|
function is a built-in function. Since Python 3.10, :func:`!_pyio.open` is
|
2022-06-24 03:46:53 -03:00
|
|
|
also a static method.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94169`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Remove the :func:`!ssl.RAND_pseudo_bytes` function, deprecated in Python 3.6:
|
2022-06-24 06:05:53 -03:00
|
|
|
use :func:`os.urandom` or :func:`ssl.RAND_bytes` instead.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94199`.)
|
|
|
|
|
2022-06-24 06:59:32 -03:00
|
|
|
* :mod:`gzip`: Remove the ``filename`` attribute of :class:`gzip.GzipFile`,
|
|
|
|
deprecated since Python 2.6, use the :attr:`~gzip.GzipFile.name` attribute
|
|
|
|
instead. In write mode, the ``filename`` attribute added ``'.gz'`` file
|
|
|
|
extension if it was not present.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94196`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Remove the :func:`!ssl.match_hostname` function.
|
|
|
|
It was deprecated in Python 3.7. OpenSSL performs
|
2022-06-25 07:54:11 -03:00
|
|
|
hostname matching since Python 3.7, Python no longer uses the
|
2023-03-24 08:23:35 -03:00
|
|
|
:func:`!ssl.match_hostname` function.
|
2022-06-25 07:54:11 -03:00
|
|
|
(Contributed by Victor Stinner in :gh:`94199`.)
|
2022-05-16 14:52:08 -03:00
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Remove the :func:`!locale.format` function, deprecated in Python 3.7:
|
2022-06-26 07:41:19 -03:00
|
|
|
use :func:`locale.format_string` instead.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94226`.)
|
|
|
|
|
2022-06-28 06:51:13 -03:00
|
|
|
* :mod:`hashlib`: Remove the pure Python implementation of
|
|
|
|
:func:`hashlib.pbkdf2_hmac()`, deprecated in Python 3.10. Python 3.10 and
|
|
|
|
newer requires OpenSSL 1.1.1 (:pep:`644`): this OpenSSL version provides
|
|
|
|
a C implementation of :func:`~hashlib.pbkdf2_hmac()` which is faster.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94199`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* :mod:`xml.etree.ElementTree`: Remove the ``ElementTree.Element.copy()`` method of the
|
2022-07-04 10:51:01 -03:00
|
|
|
pure Python implementation, deprecated in Python 3.10, use the
|
2023-03-24 08:23:35 -03:00
|
|
|
:func:`copy.copy` function instead. The C implementation of :mod:`xml.etree.ElementTree`
|
2022-07-04 10:51:01 -03:00
|
|
|
has no ``copy()`` method, only a ``__copy__()`` method.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94383`.)
|
|
|
|
|
2022-07-05 07:11:42 -03:00
|
|
|
* :mod:`zipimport`: Remove ``find_loader()`` and ``find_module()`` methods,
|
|
|
|
deprecated in Python 3.10: use the ``find_spec()`` method instead. See
|
|
|
|
:pep:`451` for the rationale.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94379`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Remove the :func:`!ssl.wrap_socket` function, deprecated in Python 3.7:
|
2022-07-08 10:20:15 -03:00
|
|
|
instead, create a :class:`ssl.SSLContext` object and call its
|
|
|
|
:class:`ssl.SSLContext.wrap_socket` method. Any package that still uses
|
2023-03-24 08:23:35 -03:00
|
|
|
:func:`!ssl.wrap_socket` is broken and insecure. The function neither sends a
|
2022-07-08 10:20:15 -03:00
|
|
|
SNI TLS extension nor validates server hostname. Code is subject to `CWE-295
|
|
|
|
<https://cwe.mitre.org/data/definitions/295.html>`_: Improper Certificate
|
|
|
|
Validation.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94199`.)
|
|
|
|
|
2022-10-05 15:42:26 -03:00
|
|
|
* Many previously deprecated cleanups in :mod:`importlib` have now been
|
|
|
|
completed:
|
|
|
|
|
|
|
|
* References to, and support for ``module_repr()`` has been eradicated.
|
|
|
|
|
2022-06-26 07:41:19 -03:00
|
|
|
|
2022-10-05 19:00:45 -03:00
|
|
|
* ``importlib.util.set_package`` has been removed.
|
|
|
|
(Contributed by Brett Cannon in :gh:`65961`.)
|
|
|
|
|
2022-10-11 10:31:33 -03:00
|
|
|
* Removed the ``suspicious`` rule from the documentation Makefile, and
|
|
|
|
removed ``Doc/tools/rstlint.py``, both in favor of `sphinx-lint
|
|
|
|
<https://github.com/sphinx-contrib/sphinx-lint>`_.
|
|
|
|
(Contributed by Julien Palard in :gh:`98179`.)
|
|
|
|
|
2022-12-28 15:43:19 -04:00
|
|
|
* Remove the *keyfile* and *certfile* parameters from the
|
|
|
|
:mod:`ftplib`, :mod:`imaplib`, :mod:`poplib` and :mod:`smtplib` modules,
|
|
|
|
and the *key_file*, *cert_file* and *check_hostname* parameters from the
|
|
|
|
:mod:`http.client` module,
|
|
|
|
all deprecated since Python 3.6. Use the *context* parameter
|
2022-11-03 14:32:25 -03:00
|
|
|
(*ssl_context* in :mod:`imaplib`) instead.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94172`.)
|
|
|
|
|
|
|
|
* :mod:`ftplib`: Remove the ``FTP_TLS.ssl_version`` class attribute: use the
|
|
|
|
*context* parameter instead.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94172`.)
|
|
|
|
|
2023-03-31 12:02:47 -03:00
|
|
|
* Remove support for obsolete browsers from :mod:`webbrowser`.
|
|
|
|
Removed browsers include: Grail, Mosaic, Netscape, Galeon, Skipstone,
|
|
|
|
Iceape, Firebird, and Firefox versions 35 and below (:gh:`102871`).
|
|
|
|
|
2022-10-05 19:00:45 -03:00
|
|
|
|
2022-05-07 23:40:52 -03:00
|
|
|
Porting to Python 3.12
|
|
|
|
======================
|
|
|
|
|
|
|
|
This section lists previously described changes and other bugfixes
|
|
|
|
that may require changes to your code.
|
2022-05-08 13:19:29 -03:00
|
|
|
|
|
|
|
Changes in the Python API
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
* More strict rules are now applied for numerical group references and
|
|
|
|
group names in regular expressions.
|
|
|
|
Only sequence of ASCII digits is now accepted as a numerical reference.
|
|
|
|
The group name in bytes patterns and replacement strings can now only
|
|
|
|
contain ASCII letters and digits and underscore.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`91760`.)
|
2022-05-09 09:26:30 -03:00
|
|
|
|
2023-01-21 04:53:54 -04:00
|
|
|
* Removed ``randrange()`` functionality deprecated since Python 3.10. Formerly,
|
|
|
|
``randrange(10.0)`` losslessly converted to ``randrange(10)``. Now, it raises a
|
|
|
|
:exc:`TypeError`. Also, the exception raised for non-integral values such as
|
|
|
|
``randrange(10.5)`` or ``randrange('10')`` has been changed from :exc:`ValueError` to
|
|
|
|
:exc:`TypeError`. This also prevents bugs where ``randrange(1e25)`` would silently
|
2022-05-12 01:54:51 -03:00
|
|
|
select from a larger range than ``randrange(10**25)``.
|
2023-01-21 04:53:54 -04:00
|
|
|
(Originally suggested by Serhiy Storchaka :gh:`86388`.)
|
2022-05-12 01:54:51 -03:00
|
|
|
|
2022-06-23 00:09:57 -03:00
|
|
|
* :class:`argparse.ArgumentParser` changed encoding and error handler
|
|
|
|
for reading arguments from file (e.g. ``fromfile_prefix_chars`` option)
|
|
|
|
from default text encoding (e.g. :func:`locale.getpreferredencoding(False) <locale.getpreferredencoding>`)
|
|
|
|
to :term:`filesystem encoding and error handler`.
|
|
|
|
Argument files should be encoded in UTF-8 instead of ANSI Codepage on Windows.
|
|
|
|
|
2022-08-05 21:41:29 -03:00
|
|
|
* Removed the ``asyncore``-based ``smtpd`` module deprecated in Python 3.4.7
|
|
|
|
and 3.5.4. A recommended replacement is the
|
|
|
|
:mod:`asyncio`-based aiosmtpd_ PyPI module.
|
|
|
|
|
2022-07-04 10:29:19 -03:00
|
|
|
* :func:`shlex.split`: Passing ``None`` for *s* argument now raises an
|
|
|
|
exception, rather than reading :data:`sys.stdin`. The feature was deprecated
|
|
|
|
in Python 3.9.
|
|
|
|
(Contributed by Victor Stinner in :gh:`94352`.)
|
|
|
|
|
2022-10-18 12:52:31 -03:00
|
|
|
* The :mod:`os` module no longer accepts bytes-like paths, like
|
|
|
|
:class:`bytearray` and :class:`memoryview` types: only the exact
|
|
|
|
:class:`bytes` type is accepted for bytes strings.
|
|
|
|
(Contributed by Victor Stinner in :gh:`98393`.)
|
|
|
|
|
2022-11-29 18:58:20 -04:00
|
|
|
* :func:`syslog.openlog` and :func:`syslog.closelog` now fail if used in subinterpreters.
|
|
|
|
:func:`syslog.syslog` may still be used in subinterpreters,
|
|
|
|
but now only if :func:`syslog.openlog` has already been called in the main interpreter.
|
|
|
|
These new restrictions do not apply to the main interpreter,
|
|
|
|
so only a very small set of users might be affected.
|
|
|
|
This change helps with interpreter isolation. Furthermore, :mod:`syslog` is a wrapper
|
|
|
|
around process-global resources, which are best managed from the main interpreter.
|
|
|
|
(Contributed by Dong-hee Na in :gh:`99127`.)
|
|
|
|
|
2023-02-22 21:49:22 -04:00
|
|
|
* The undocumented locking behavior of :func:`~functools.cached_property`
|
|
|
|
is removed, because it locked across all instances of the class, leading to high
|
|
|
|
lock contention. This means that a cached property getter function could now run
|
|
|
|
more than once for a single instance, if two threads race. For most simple
|
|
|
|
cached properties (e.g. those that are idempotent and simply calculate a value
|
|
|
|
based on other attributes of the instance) this will be fine. If
|
|
|
|
synchronization is needed, implement locking within the cached property getter
|
|
|
|
function or around multi-threaded access points.
|
|
|
|
|
2023-04-11 05:38:37 -03:00
|
|
|
* :func:`sys._current_exceptions` now returns a mapping from thread-id to an
|
|
|
|
exception instance, rather than to a ``(typ, exc, tb)`` tuple.
|
|
|
|
(Contributed by Irit Katriel in :gh:`103176`.)
|
|
|
|
|
2022-05-09 09:26:30 -03:00
|
|
|
|
|
|
|
Build Changes
|
|
|
|
=============
|
|
|
|
|
2022-07-14 04:51:49 -03:00
|
|
|
* Python no longer uses ``setup.py`` to build shared C extension modules.
|
|
|
|
Build parameters like headers and libraries are detected in ``configure``
|
|
|
|
script. Extensions are built by ``Makefile``. Most extensions use
|
|
|
|
``pkg-config`` and fall back to manual detection.
|
|
|
|
(Contributed by Christian Heimes in :gh:`93939`.)
|
|
|
|
|
2022-05-27 08:30:45 -03:00
|
|
|
* ``va_start()`` with two parameters, like ``va_start(args, format),``
|
|
|
|
is now required to build Python.
|
|
|
|
``va_start()`` is no longer called with a single parameter.
|
|
|
|
(Contributed by Kumar Aditya in :gh:`93207`.)
|
|
|
|
|
2022-09-16 07:40:05 -03:00
|
|
|
* CPython now uses the ThinLTO option as the default link time optimization policy
|
|
|
|
if the Clang compiler accepts the flag.
|
|
|
|
(Contributed by Dong-hee Na in :gh:`89536`.)
|
|
|
|
|
2022-11-14 08:43:45 -04:00
|
|
|
* Add ``COMPILEALL_OPTS`` variable in Makefile to override :mod:`compileall`
|
|
|
|
options (default: ``-j0``) in ``make install``. Also merged the 3
|
|
|
|
``compileall`` commands into a single command to build .pyc files for all
|
|
|
|
optimization levels (0, 1, 2) at once.
|
|
|
|
(Contributed by Victor Stinner in :gh:`99289`.)
|
|
|
|
|
2022-05-09 09:26:30 -03:00
|
|
|
|
|
|
|
C API Changes
|
|
|
|
=============
|
|
|
|
|
|
|
|
New Features
|
|
|
|
------------
|
|
|
|
|
2023-02-28 04:31:01 -04:00
|
|
|
|
|
|
|
* :pep:`697`: Introduced the :ref:`Unstable C API tier <unstable-c-api>`,
|
|
|
|
intended for low-level tools like debuggers and JIT compilers.
|
|
|
|
This API may change in each minor release of CPython without deprecation
|
|
|
|
warnings.
|
|
|
|
Its contents are marked by the ``PyUnstable_`` prefix in names.
|
|
|
|
|
|
|
|
Code object constructors:
|
|
|
|
|
|
|
|
- ``PyUnstable_Code_New()`` (renamed from ``PyCode_New``)
|
|
|
|
- ``PyUnstable_Code_NewWithPosOnlyArgs()`` (renamed from ``PyCode_NewWithPosOnlyArgs``)
|
|
|
|
|
|
|
|
Extra storage for code objects (:pep:`523`):
|
|
|
|
|
|
|
|
- ``PyUnstable_Eval_RequestCodeExtraIndex()`` (renamed from ``_PyEval_RequestCodeExtraIndex``)
|
|
|
|
- ``PyUnstable_Code_GetExtra()`` (renamed from ``_PyCode_GetExtra``)
|
|
|
|
- ``PyUnstable_Code_SetExtra()`` (renamed from ``_PyCode_SetExtra``)
|
|
|
|
|
|
|
|
The original names will continue to be available until the respective
|
|
|
|
API changes.
|
|
|
|
|
|
|
|
(Contributed by Petr Viktorin in :gh:`101101`.)
|
|
|
|
|
2022-05-27 05:27:39 -03:00
|
|
|
* Added the new limited C API function :c:func:`PyType_FromMetaclass`,
|
|
|
|
which generalizes the existing :c:func:`PyType_FromModuleAndSpec` using
|
|
|
|
an additional metaclass argument.
|
|
|
|
(Contributed by Wenzel Jakob in :gh:`93012`.)
|
|
|
|
|
2022-08-08 09:12:05 -03:00
|
|
|
* API for creating objects that can be called using
|
|
|
|
:ref:`the vectorcall protocol <vectorcall>` was added to the
|
|
|
|
:ref:`Limited API <stable>`:
|
|
|
|
|
|
|
|
* :const:`Py_TPFLAGS_HAVE_VECTORCALL`
|
|
|
|
* :c:func:`PyVectorcall_NARGS`
|
|
|
|
* :c:func:`PyVectorcall_Call`
|
|
|
|
* :c:type:`vectorcallfunc`
|
|
|
|
|
2022-08-04 12:19:29 -03:00
|
|
|
The :const:`Py_TPFLAGS_HAVE_VECTORCALL` flag is now removed from a class
|
|
|
|
when the class's :py:meth:`~object.__call__` method is reassigned.
|
|
|
|
This makes vectorcall safe to use with mutable types (i.e. heap types
|
2023-03-24 08:23:35 -03:00
|
|
|
without the immutable flag, :const:`Py_TPFLAGS_IMMUTABLETYPE`).
|
2022-08-04 12:19:29 -03:00
|
|
|
Mutable types that do not override :c:member:`~PyTypeObject.tp_call` now
|
2022-08-08 09:12:05 -03:00
|
|
|
inherit the ``Py_TPFLAGS_HAVE_VECTORCALL`` flag.
|
|
|
|
(Contributed by Petr Viktorin in :gh:`93274`.)
|
2022-08-04 12:19:29 -03:00
|
|
|
|
2022-08-17 08:50:53 -03:00
|
|
|
The :const:`Py_TPFLAGS_MANAGED_DICT` and :const:`Py_TPFLAGS_MANAGED_WEAKREF`
|
|
|
|
flags have been added. This allows extensions classes to support object
|
|
|
|
``__dict__`` and weakrefs with less bookkeeping,
|
|
|
|
using less memory and with faster access.
|
|
|
|
|
2022-11-06 18:54:55 -04:00
|
|
|
* API for performing calls using
|
|
|
|
:ref:`the vectorcall protocol <vectorcall>` was added to the
|
|
|
|
:ref:`Limited API <stable>`:
|
|
|
|
|
|
|
|
* :c:func:`PyObject_Vectorcall`
|
|
|
|
* :c:func:`PyObject_VectorcallMethod`
|
|
|
|
* :const:`PY_VECTORCALL_ARGUMENTS_OFFSET`
|
|
|
|
|
|
|
|
This means that both the incoming and outgoing ends of the vector call
|
|
|
|
protocol are now available in the :ref:`Limited API <stable>`. (Contributed
|
|
|
|
by Wenzel Jakob in :gh:`98586`.)
|
|
|
|
|
2022-09-13 09:12:15 -03:00
|
|
|
* Added two new public functions,
|
|
|
|
:c:func:`PyEval_SetProfileAllThreads` and
|
|
|
|
:c:func:`PyEval_SetTraceAllThreads`, that allow to set tracing and profiling
|
|
|
|
functions in all running threads in addition to the calling one. (Contributed
|
|
|
|
by Pablo Galindo in :gh:`93503`.)
|
|
|
|
|
2022-09-15 12:42:37 -03:00
|
|
|
* Added new function :c:func:`PyFunction_SetVectorcall` to the C API
|
|
|
|
which sets the vectorcall field of a given :c:type:`PyFunctionObject`.
|
|
|
|
(Contributed by Andrew Frost in :gh:`92257`.)
|
|
|
|
|
2022-10-07 21:37:46 -03:00
|
|
|
* The C API now permits registering callbacks via :c:func:`PyDict_AddWatcher`,
|
2023-03-24 08:23:35 -03:00
|
|
|
:c:func:`PyDict_Watch` and related APIs to be called whenever a dictionary
|
2022-10-07 21:37:46 -03:00
|
|
|
is modified. This is intended for use by optimizing interpreters, JIT
|
|
|
|
compilers, or debuggers.
|
2022-10-21 10:41:51 -03:00
|
|
|
(Contributed by Carl Meyer in :gh:`91052`.)
|
|
|
|
|
|
|
|
* Added :c:func:`PyType_AddWatcher` and :c:func:`PyType_Watch` API to register
|
|
|
|
callbacks to receive notification on changes to a type.
|
|
|
|
(Contributed by Carl Meyer in :gh:`91051`.)
|
|
|
|
|
2022-12-02 13:28:27 -04:00
|
|
|
* Added :c:func:`PyCode_AddWatcher` and :c:func:`PyCode_ClearWatcher`
|
|
|
|
APIs to register callbacks to receive notification on creation and
|
|
|
|
destruction of code objects.
|
|
|
|
(Contributed by Itamar Ostricher in :gh:`91054`.)
|
2022-10-07 21:37:46 -03:00
|
|
|
|
2022-11-08 12:40:27 -04:00
|
|
|
* Add :c:func:`PyFrame_GetVar` and :c:func:`PyFrame_GetVarString` functions to
|
|
|
|
get a frame variable by its name.
|
|
|
|
(Contributed by Victor Stinner in :gh:`91248`.)
|
|
|
|
|
2023-02-23 08:19:21 -04:00
|
|
|
* Add :c:func:`PyErr_GetRaisedException` and :c:func:`PyErr_SetRaisedException`
|
|
|
|
for saving and restoring the current exception.
|
|
|
|
These functions return and accept a single exception object,
|
|
|
|
rather than the triple arguments of the now-deprecated
|
|
|
|
:c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore`.
|
|
|
|
This is less error prone and a bit more efficient.
|
|
|
|
(Contributed by Mark Shannon in :gh:`101578`.)
|
|
|
|
|
2023-04-01 17:30:23 -03:00
|
|
|
* Add ``_PyErr_ChainExceptions1``, which takes an exception instance,
|
|
|
|
to replace the legacy-API ``_PyErr_ChainExceptions``, which is now
|
|
|
|
deprecated. (Contributed by Mark Shannon in :gh:`101578`.)
|
|
|
|
|
2023-02-23 08:19:21 -04:00
|
|
|
* Add :c:func:`PyException_GetArgs` and :c:func:`PyException_SetArgs`
|
|
|
|
as convenience functions for retrieving and modifying
|
|
|
|
the :attr:`~BaseException.args` passed to the exception's constructor.
|
|
|
|
(Contributed by Mark Shannon in :gh:`101578`.)
|
|
|
|
|
2023-03-16 19:18:04 -03:00
|
|
|
* Add :c:func:`PyErr_DisplayException`, which takes an exception instance,
|
2023-03-24 08:23:35 -03:00
|
|
|
to replace the legacy-api :c:func:`!PyErr_Display`. (Contributed by
|
2023-03-16 19:18:04 -03:00
|
|
|
Irit Katriel in :gh:`102755`).
|
|
|
|
|
2022-05-09 09:26:30 -03:00
|
|
|
Porting to Python 3.12
|
|
|
|
----------------------
|
|
|
|
|
2022-05-12 02:48:38 -03:00
|
|
|
* Legacy Unicode APIs based on ``Py_UNICODE*`` representation has been removed.
|
|
|
|
Please migrate to APIs based on UTF-8 or ``wchar_t*``.
|
|
|
|
|
|
|
|
* Argument parsing functions like :c:func:`PyArg_ParseTuple` doesn't support
|
|
|
|
``Py_UNICODE*`` based format (e.g. ``u``, ``Z``) anymore. Please migrate
|
|
|
|
to other formats for Unicode like ``s``, ``z``, ``es``, and ``U``.
|
|
|
|
|
2022-07-28 22:23:47 -03:00
|
|
|
* ``tp_weaklist`` for all static builtin types is always ``NULL``.
|
|
|
|
This is an internal-only field on ``PyTypeObject``
|
|
|
|
but we're pointing out the change in case someone happens to be
|
|
|
|
accessing the field directly anyway. To avoid breakage, consider
|
|
|
|
using the existing public C-API instead, or, if necessary, the
|
|
|
|
(internal-only) ``_PyObject_GET_WEAKREFS_LISTPTR()`` macro.
|
|
|
|
|
2022-08-04 22:26:59 -03:00
|
|
|
* This internal-only :c:member:`PyTypeObject.tp_subclasses` may now not be
|
|
|
|
a valid object pointer. Its type was changed to :c:expr:`void *` to
|
|
|
|
reflect this. We mention this in case someone happens to be accessing the
|
|
|
|
internal-only field directly.
|
|
|
|
|
|
|
|
To get a list of subclasses, call the Python method
|
|
|
|
:py:meth:`~class.__subclasses__` (using :c:func:`PyObject_CallMethod`,
|
|
|
|
for example).
|
|
|
|
|
2022-08-08 13:21:07 -03:00
|
|
|
* An unrecognized format character in :c:func:`PyUnicode_FromFormat` and
|
|
|
|
:c:func:`PyUnicode_FromFormatV` now sets a :exc:`SystemError`.
|
|
|
|
In previous versions it caused all the rest of the format string to be
|
|
|
|
copied as-is to the result string, and any extra arguments discarded.
|
|
|
|
(Contributed by Serhiy Storchaka in :gh:`95781`.)
|
|
|
|
|
2022-08-10 08:12:40 -03:00
|
|
|
* Fixed wrong sign placement in :c:func:`PyUnicode_FromFormat` and
|
|
|
|
:c:func:`PyUnicode_FromFormatV`.
|
|
|
|
(Contributed by Philip Georgi in :gh:`95504`.)
|
2022-08-04 22:26:59 -03:00
|
|
|
|
2022-08-17 08:50:53 -03:00
|
|
|
* Extension classes wanting to add a ``__dict__`` or weak reference slot
|
|
|
|
should use :const:`Py_TPFLAGS_MANAGED_DICT` and
|
|
|
|
:const:`Py_TPFLAGS_MANAGED_WEAKREF` instead of ``tp_dictoffset`` and
|
|
|
|
``tp_weaklistoffset``, respectively.
|
|
|
|
The use of ``tp_dictoffset`` and ``tp_weaklistoffset`` is still
|
|
|
|
supported, but does not fully support multiple inheritance
|
2022-10-06 22:01:30 -03:00
|
|
|
(:gh:`95589`), and performance may be worse.
|
2022-08-17 08:50:53 -03:00
|
|
|
Classes declaring :const:`Py_TPFLAGS_MANAGED_DICT` should call
|
2023-03-24 08:23:35 -03:00
|
|
|
:c:func:`!_PyObject_VisitManagedDict` and :c:func:`!_PyObject_ClearManagedDict`
|
2022-08-17 08:50:53 -03:00
|
|
|
to traverse and clear their instance's dictionaries.
|
|
|
|
To clear weakrefs, call :c:func:`PyObject_ClearWeakRefs`, as before.
|
|
|
|
|
2022-10-18 12:52:31 -03:00
|
|
|
* The :c:func:`PyUnicode_FSDecoder` function no longer accepts bytes-like
|
|
|
|
paths, like :class:`bytearray` and :class:`memoryview` types: only the exact
|
|
|
|
:class:`bytes` type is accepted for bytes strings.
|
|
|
|
(Contributed by Victor Stinner in :gh:`98393`.)
|
|
|
|
|
2022-12-07 10:22:38 -04:00
|
|
|
* The :c:macro:`Py_CLEAR`, :c:macro:`Py_SETREF` and :c:macro:`Py_XSETREF`
|
|
|
|
macros now only evaluate their arguments once. If an argument has side
|
|
|
|
effects, these side effects are no longer duplicated.
|
|
|
|
(Contributed by Victor Stinner in :gh:`98724`.)
|
|
|
|
|
2023-03-14 19:38:15 -03:00
|
|
|
* The interpreter's error indicator is now always normalized. This means
|
|
|
|
that :c:func:`PyErr_SetObject`, :c:func:`PyErr_SetString` and the other
|
|
|
|
functions that set the error indicator now normalize the exception
|
|
|
|
before storing it. (Contributed by Mark Shannon in :gh:`101578`.)
|
|
|
|
|
2023-03-20 13:35:49 -03:00
|
|
|
* ``_Py_RefTotal`` is no longer authoritative and only kept around
|
|
|
|
for ABI compabitility. Note that it is an internal global and only
|
|
|
|
available on debug builds. If you happen to be using it then you'll
|
|
|
|
need to start using ``_Py_GetGlobalRefTotal()``.
|
|
|
|
|
2022-05-09 09:26:30 -03:00
|
|
|
Deprecated
|
|
|
|
----------
|
|
|
|
|
2022-06-17 11:12:00 -03:00
|
|
|
* Deprecate global configuration variable:
|
|
|
|
|
|
|
|
* :c:var:`Py_DebugFlag`: use :c:member:`PyConfig.parser_debug`
|
|
|
|
* :c:var:`Py_VerboseFlag`: use :c:member:`PyConfig.verbose`
|
|
|
|
* :c:var:`Py_QuietFlag`: use :c:member:`PyConfig.quiet`
|
|
|
|
* :c:var:`Py_InteractiveFlag`: use :c:member:`PyConfig.interactive`
|
|
|
|
* :c:var:`Py_InspectFlag`: use :c:member:`PyConfig.inspect`
|
|
|
|
* :c:var:`Py_OptimizeFlag`: use :c:member:`PyConfig.optimization_level`
|
|
|
|
* :c:var:`Py_NoSiteFlag`: use :c:member:`PyConfig.site_import`
|
|
|
|
* :c:var:`Py_BytesWarningFlag`: use :c:member:`PyConfig.bytes_warning`
|
|
|
|
* :c:var:`Py_FrozenFlag`: use :c:member:`PyConfig.pathconfig_warnings`
|
|
|
|
* :c:var:`Py_IgnoreEnvironmentFlag`: use :c:member:`PyConfig.use_environment`
|
|
|
|
* :c:var:`Py_DontWriteBytecodeFlag`: use :c:member:`PyConfig.write_bytecode`
|
|
|
|
* :c:var:`Py_NoUserSiteDirectory`: use :c:member:`PyConfig.user_site_directory`
|
|
|
|
* :c:var:`Py_UnbufferedStdioFlag`: use :c:member:`PyConfig.buffered_stdio`
|
|
|
|
* :c:var:`Py_HashRandomizationFlag`: use :c:member:`PyConfig.use_hash_seed`
|
|
|
|
and :c:member:`PyConfig.hash_seed`
|
|
|
|
* :c:var:`Py_IsolatedFlag`: use :c:member:`PyConfig.isolated`
|
2023-03-24 08:23:35 -03:00
|
|
|
* :c:var:`Py_LegacyWindowsFSEncodingFlag`: use :c:member:`PyPreConfig.legacy_windows_fs_encoding`
|
2022-06-17 11:12:00 -03:00
|
|
|
* :c:var:`Py_LegacyWindowsStdioFlag`: use :c:member:`PyConfig.legacy_windows_stdio`
|
2023-03-24 08:23:35 -03:00
|
|
|
* :c:var:`!Py_FileSystemDefaultEncoding`: use :c:member:`PyConfig.filesystem_encoding`
|
|
|
|
* :c:var:`!Py_FileSystemDefaultEncodeErrors`: use :c:member:`PyConfig.filesystem_errors`
|
|
|
|
* :c:var:`!Py_UTF8Mode`: use :c:member:`PyPreConfig.utf8_mode` (see :c:func:`Py_PreInitialize`)
|
2022-06-17 11:12:00 -03:00
|
|
|
|
|
|
|
The :c:func:`Py_InitializeFromConfig` API should be used with
|
|
|
|
:c:type:`PyConfig` instead.
|
|
|
|
(Contributed by Victor Stinner in :gh:`77782`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* Creating immutable types (:const:`Py_TPFLAGS_IMMUTABLETYPE`) with mutable
|
2022-08-04 11:13:45 -03:00
|
|
|
bases is deprecated and will be disabled in Python 3.14.
|
|
|
|
|
gh-47146: Soft-deprecate structmember.h, expose its contents via Python.h (GH-99014)
The ``structmember.h`` header is deprecated, though it continues to be available
and there are no plans to remove it. There are no deprecation warnings. Old code
can stay unchanged (unless the extra include and non-namespaced macros bother
you greatly). Specifically, no uses in CPython are updated -- that would just be
unnecessary churn.
The ``structmember.h`` header is deprecated, though it continues to be
available and there are no plans to remove it.
Its contents are now available just by including ``Python.h``,
with a ``Py`` prefix added if it was missing:
- `PyMemberDef`, `PyMember_GetOne` and`PyMember_SetOne`
- Type macros like `Py_T_INT`, `Py_T_DOUBLE`, etc.
(previously ``T_INT``, ``T_DOUBLE``, etc.)
- The flags `Py_READONLY` (previously ``READONLY``) and
`Py_AUDIT_READ` (previously all uppercase)
Several items are not exposed from ``Python.h``:
- `T_OBJECT` (use `Py_T_OBJECT_EX`)
- `T_NONE` (previously undocumented, and pretty quirky)
- The macro ``WRITE_RESTRICTED`` which does nothing.
- The macros ``RESTRICTED`` and ``READ_RESTRICTED``, equivalents of
`Py_AUDIT_READ`.
- In some configurations, ``<stddef.h>`` is not included from ``Python.h``.
It should be included manually when using ``offsetof()``.
The deprecated header continues to provide its original
contents under the original names.
Your old code can stay unchanged, unless the extra include and non-namespaced
macros bother you greatly.
There is discussion on the issue to rename `T_PYSSIZET` to `PY_T_SSIZE` or
similar. I chose not to do that -- users will probably copy/paste that with any
spelling, and not renaming it makes migration docs simpler.
Co-Authored-By: Alexander Belopolsky <abalkin@users.noreply.github.com>
Co-Authored-By: Matthias Braun <MatzeB@users.noreply.github.com>
2022-11-22 03:25:43 -04:00
|
|
|
* The ``structmember.h`` header is deprecated, though it continues to be
|
|
|
|
available and there are no plans to remove it.
|
|
|
|
|
|
|
|
Its contents are now available just by including ``Python.h``,
|
|
|
|
with a ``Py`` prefix added if it was missing:
|
|
|
|
|
|
|
|
- :c:struct:`PyMemberDef`, :c:func:`PyMember_GetOne` and
|
|
|
|
:c:func:`PyMember_SetOne`
|
|
|
|
- Type macros like :c:macro:`Py_T_INT`, :c:macro:`Py_T_DOUBLE`, etc.
|
|
|
|
(previously ``T_INT``, ``T_DOUBLE``, etc.)
|
|
|
|
- The flags :c:macro:`Py_READONLY` (previously ``READONLY``) and
|
|
|
|
:c:macro:`Py_AUDIT_READ` (previously all uppercase)
|
|
|
|
|
|
|
|
Several items are not exposed from ``Python.h``:
|
|
|
|
|
|
|
|
- :c:macro:`T_OBJECT` (use :c:macro:`Py_T_OBJECT_EX`)
|
|
|
|
- :c:macro:`T_NONE` (previously undocumented, and pretty quirky)
|
|
|
|
- The macro ``WRITE_RESTRICTED`` which does nothing.
|
|
|
|
- The macros ``RESTRICTED`` and ``READ_RESTRICTED``, equivalents of
|
|
|
|
:c:macro:`Py_AUDIT_READ`.
|
|
|
|
- In some configurations, ``<stddef.h>`` is not included from ``Python.h``.
|
|
|
|
It should be included manually when using ``offsetof()``.
|
|
|
|
|
|
|
|
The deprecated header continues to provide its original
|
|
|
|
contents under the original names.
|
|
|
|
Your old code can stay unchanged, unless the extra include and non-namespaced
|
|
|
|
macros bother you greatly.
|
|
|
|
|
|
|
|
(Contributed in :gh:`47146` by Petr Viktorin, based on
|
|
|
|
earlier work by Alexander Belopolsky and Matthias Braun.)
|
|
|
|
|
2023-02-23 08:19:21 -04:00
|
|
|
* :c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` are deprecated.
|
|
|
|
Use :c:func:`PyErr_GetRaisedException` and
|
|
|
|
:c:func:`PyErr_SetRaisedException` instead.
|
|
|
|
(Contributed by Mark Shannon in :gh:`101578`.)
|
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* :c:func:`!PyErr_Display` is deprecated. Use :c:func:`PyErr_DisplayException`
|
2023-03-16 19:18:04 -03:00
|
|
|
instead. (Contributed by Irit Katriel in :gh:`102755`).
|
|
|
|
|
2023-04-01 17:30:23 -03:00
|
|
|
* ``_PyErr_ChainExceptions`` is deprecated. Use ``_PyErr_ChainExceptions1``
|
|
|
|
instead. (Contributed by Irit Katriel in :gh:`102192`.)
|
2022-06-17 11:12:00 -03:00
|
|
|
|
2022-05-09 09:26:30 -03:00
|
|
|
Removed
|
|
|
|
-------
|
2022-05-11 18:22:50 -03:00
|
|
|
|
|
|
|
* Remove the ``token.h`` header file. There was never any public tokenizer C
|
|
|
|
API. The ``token.h`` header file was only designed to be used by Python
|
|
|
|
internals.
|
|
|
|
(Contributed by Victor Stinner in :gh:`92651`.)
|
2022-05-12 02:48:38 -03:00
|
|
|
|
2023-01-20 18:10:08 -04:00
|
|
|
* Legacy Unicode APIs have been removed. See :pep:`623` for detail.
|
2022-05-12 02:48:38 -03:00
|
|
|
|
2023-03-24 08:23:35 -03:00
|
|
|
* :c:macro:`!PyUnicode_WCHAR_KIND`
|
|
|
|
* :c:func:`!PyUnicode_AS_UNICODE`
|
|
|
|
* :c:func:`!PyUnicode_AsUnicode`
|
|
|
|
* :c:func:`!PyUnicode_AsUnicodeAndSize`
|
|
|
|
* :c:func:`!PyUnicode_AS_DATA`
|
|
|
|
* :c:func:`!PyUnicode_FromUnicode`
|
|
|
|
* :c:func:`!PyUnicode_GET_SIZE`
|
|
|
|
* :c:func:`!PyUnicode_GetSize`
|
|
|
|
* :c:func:`!PyUnicode_GET_DATA_SIZE`
|
2022-05-13 08:40:22 -03:00
|
|
|
|
|
|
|
* Remove the ``PyUnicode_InternImmortal()`` function and the
|
|
|
|
``SSTATE_INTERNED_IMMORTAL`` macro.
|
|
|
|
(Contributed by Victor Stinner in :gh:`85858`.)
|
2022-11-19 02:25:32 -04:00
|
|
|
|
2022-12-23 16:17:24 -04:00
|
|
|
* Remove ``Jython`` compatibility hacks from several stdlib modules and tests.
|
|
|
|
(Contributed by Nikita Sobolev in :gh:`99482`.)
|
|
|
|
|
2022-11-19 02:25:32 -04:00
|
|
|
* Remove ``_use_broken_old_ctypes_structure_semantics_`` flag
|
|
|
|
from :mod:`ctypes` module.
|
|
|
|
(Contributed by Nikita Sobolev in :gh:`99285`.)
|