Mailman 3 January 2022 - Python-Dev

PEP 678: Enriching Exceptions with Notes
by Zac Hatfield Dodds April 12, 2022

April 12, 2022

Hi all, I've written PEP 678, proposing the addition of a __note__ attribute which can be used to enrich displayed exceptions. This is particularly useful with ExceptionGroup, or where exception chaining is unsuitable, and ensures that 'orphan' output is not produced if the annotated exception is caught. Link to the PEP: https://www.python.org/dev/peps/pep-0678/ *Please, redirect all discussions to:* https://discuss.python.org/t/pep-678-enriching-exceptions-with-notes/13374 Thanks for your time, and to those who have already made (very helpful!) comments! Best wishes from just-moved-to San Francisco, Zac Hatfield-Dodds

2 1

RFC on PEP 655: Required[] and NotRequired[] for TypedDict
by David Foster March 10, 2022

March 10, 2022

This PEP [1] introduces syntax to mark individual keys of a TypedDict as either required or potentially-missing. Previously the only way to have a TypedDict with mixed required and non-required keys was to define two TypedDicts - one with total=True and one with total=False - and have one of those TypedDicts inherit from the other. This PEP introduces special forms Required[] and NotRequired[] to the "typing" module that can be used to directly mark individual items of a TypedDict as required or not-required. We have implementations for mypy, pyright, and pyanalyze. Consensus on the PEP has been reached in typing-sig. My understanding of the PEP process as described in PEP 1 [2] is that content review should be requested of core developers here in python-dev. So consider this my official request for comments! ^_^ I believe that after review & feedback from python-dev the next step would be to submit this PEP to the Steering Council. However it's not clear to me from [2] where I should actually do that when the time comes. -- David Foster | Seattle, WA, USA Contributor to TypedDict support for mypy [1]: https://www.python.org/dev/peps/pep-0655/ [2]: https://www.python.org/dev/peps/pep-0001/#pep-review-resolution

4 6

Suggestion: a little language for type definitions
by jack.jansen＠cwi.nl Feb. 10, 2022

Feb. 10, 2022

I posted this suggestion earlier in the callable type syntax discussion, at which point it was completely ignored. Possibly because it’s a really stupid idea, but let me post it again on the off chance that it isn’t a stupid idea but was overlooked. > If I can make a wild suggestion: why not create a little language for type specifications? > > If you look at other programming languages you’ll see that the “type definition sub-language” is often completely different from the “execution sub-language”, with only some symbols in common and used in vaguely related ways. `bool (*myfuncptr)(int, float*)` uses a completely different set of syntactic rules than `rv = (*myfunptr)(*myintptr, &myfloat)`. So with some grains of salt you could say that C is comprised of a declarative typing sublanguage and an imperative execution sublanguage. And an even better example is Pascal, which uses a set of syntactic constructs for typing that are completely different from the execution statement syntax: `var a : array[1..10] of real` looks very different from `a[1]`, where C `float a[10]` looks pretty similar to `a[10]`. The next bit of my original email is another wild idea, the previous bit doesn’t depend on it really. I can imagine completely different ways of doing a typing sublanguage: > Python typing uses basically a subset of the execution expression syntax as its declarative typing language. > > What if we created a little language that is clearly flagged, for example as t”….” or t’….’? Then we could simply define the typestring language to be readable, so you could indeed say t”(int, str) -> bool”. And we could even allow escapes (similar to f-strings) so that the previous expression could also be specified, if you really wanted to, as t”{typing.Callable[[int, str], bool}”. -- Jack Jansen, <Jack.Jansen(a)cwi.nl>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman

15 35

"immortal" objects and how they would help per-interpreter GIL
by Eric Snow Feb. 8, 2022

Feb. 8, 2022

Most of the work toward interpreter isolation and a per-interpreter GIL involves moving static global variables to _PyRuntimeState or PyInterpreterState (or module state). Through the effort of quite a few people, we've made good progress. However, many globals still remain, with the majority being objects and most of those being static strings (e.g. _Py_Identifier), static types (incl. exceptions), and singletons. On top of that, a number of those objects are exposed in the public C-API and even in the limited API. :( Dealing with this specifically is probably the trickiest thing I've had to work through in this project. There is one solution that would help both of the above in a nice way: "immortal" objects. The idea of objects that never get deallocated isn't new and has been explored here several times. Not that long ago I tried it out by setting the refcount really high. That worked. Around the same time Eddie Elizondo at Facebook did something similar but modified Py_INCREF() and Py_DECREF() to keep the refcount from changing. Our solutions were similar but with different goals in mind. (Facebook wants to avoid copy-on-write in their pre-fork model.) A while back I concluded that neither approach would work for us. The approach I had taken would have significant cache performance penalties in a per-interpreter GIL world. The approach that modifies Py_INCREF() has a significant performance penalty due to the extra branch on such a frequent operation. Recently I've come back to the idea of immortal objects because it's much simpler than the alternate (working) solution I found. So how do we get around that performance penalty? Let's say it makes CPython 5% slower. We have some options: * live with the full penalty * make other changes to reduce the penalty to a more acceptable threshold than 5% * eliminate the penalty (e.g. claw back 5% elsewhere) * abandon all hope Mark Shannon suggested to me some things we can do. Also, from a recent conversation with Dino Viehland it sounds like Eddie was able to reach performance-neutral with a few techniques. So here are some things we can do to reduce or eliminate that penalty: * reduce refcount operations on high-activity objects (e.g. None, True, False) * reduce refcount operations in general * walk the heap at the end of runtime initialization and mark all objects as immortal * mark all global objects as immortal (statics or in _PyRuntimeState; for PyInterpreterState not needed) What do you think? Does this sound realistic? Are there additional things we can do to counter that penalty? -eric

16 35

PEP 674 – Disallow using macros as l-value (version 2)
by Victor Stinner Feb. 7, 2022

Feb. 7, 2022

Hi, I made the following changes to the PEP since the version 1 (November 30): * Elaborate the HPy section and add a new "Relationship with the HPy project" section * Elaborate which projects are impacted and which changes are needed * Remove the PyPy section The PEP can be read online: https://python.github.io/peps/ep-0674/ And you can find the plain text below. Victor PEP: 674 Title: Disallow using macros as l-value Author: Victor Stinner <vstinner(a)python.org> Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 30-Nov-2021 Python-Version: 3.11 Abstract ======== Incompatible C API change disallowing using macros as l-value to: * Allow evolving CPython internals; * Ease the C API implementation on other Python implementation; * Help migrating existing C extensions to the HPy API. On the PyPI top 5000 projects, only 14 projects (0.3%) are affected by 4 macro changes. Moreover, 24 projects just have to regenerate their Cython code to use ``Py_SET_TYPE()``. In practice, the majority of affected projects only have to make two changes: * Replace ``Py_TYPE(obj) = new_type;`` with ``Py_SET_TYPE(obj, new_type);``. * Replace ``Py_SIZE(obj) = new_size;`` with ``Py_SET_SIZE(obj, new_size);``. Rationale ========= Using a macro as a l-value -------------------------- In the Python C API, some functions are implemented as macro because writing a macro is simpler than writing a regular function. If a macro exposes directly a structure member, it is technically possible to use this macro to not only get the structure member but also set it. Example with the Python 3.10 ``Py_TYPE()`` macro:: #define Py_TYPE(ob) (((PyObject *)(ob))->ob_type) This macro can be used as a **r-value** to **get** an object type:: type = Py_TYPE(object); It can also be used as **l-value** to **set** an object type:: Py_TYPE(object) = new_type; It is also possible to set an object reference count and an object size using ``Py_REFCNT()`` and ``Py_SIZE()`` macros. Setting directly an object attribute relies on the current exact CPython implementation. Implementing this feature in other Python implementations can make their C API implementation less efficient. CPython nogil fork ------------------ Sam Gross forked Python 3.9 to remove the GIL: the `nogil branch <https://github.com/colesbury/nogil/>`_. This fork has no ``PyObject.ob_refcnt`` member, but a more elaborated implementation for reference counting, and so the ``Py_REFCNT(obj) = new_refcnt;`` code fails with a compiler error. Merging the nogil fork into the upstream CPython main branch requires first to fix this C API compatibility issue. It is a concrete example of a Python optimization blocked indirectly by the C API. This issue was already fixed in Python 3.10: the ``Py_REFCNT()`` macro has been already modified to disallow using it as a l-value. These statements are endorsed by Sam Gross (nogil developer). HPy project ----------- The `HPy project <https://hpyproject.org/>`_ is a brand new C API for Python using only handles and function calls: handles are opaque, structure members cannot be accessed directly, and pointers cannot be dereferenced. Searching and replacing ``Py_SET_SIZE()`` is easier and safer than searching and replacing some strange macro uses of ``Py_SIZE()``. ``Py_SIZE()`` can be semi-mechanically replaced by ``HPy_Length()``, whereas seeing ``Py_SET_SIZE()`` would immediately make clear that the code needs bigger changes in order to be ported to HPy (for example by using ``HPyTupleBuilder`` or ``HPyListBuilder``). The fewer internal details exposed via macros, the easier it will be for HPy to provide direct equivalents. Any macro that references "non-public" interfaces effectively exposes those interfaces publicly. These statements are endorsed by Antonio Cuni (HPy developer). GraalVM Python -------------- In GraalVM, when a Python object is accessed by the Python C API, the C API emulation layer has to wrap the GraalVM objects into wrappers that expose the internal structure of the CPython structures (PyObject, PyLongObject, PyTypeObject, etc). This is because when the C code accesses it directly or via macros, all GraalVM can intercept is a read at the struct offset, which has to be mapped back to the representation in GraalVM. The smaller the "effective" number of exposed struct members (by replacing macros with functions), the simpler GraalVM wrappers can be. This PEP alone is not enough to get rid of the wrappers in GraalVM, but it is a step towards this long term goal. GraalVM already supports HPy which is a better solution in the long term. These statements are endorsed by Tim Felgentreff (GraalVM Python developer). Specification ============= Disallow using macros as l-value -------------------------------- PyObject and PyVarObject macros ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * ``Py_TYPE()``: ``Py_SET_TYPE()`` must be used instead * ``Py_SIZE()``: ``Py_SET_SIZE()`` must be used instead "GET" macros ^^^^^^^^^^^^ * ``PyByteArray_GET_SIZE()`` * ``PyBytes_GET_SIZE()`` * ``PyCFunction_GET_CLASS()`` * ``PyCFunction_GET_FLAGS()`` * ``PyCFunction_GET_FUNCTION()`` * ``PyCFunction_GET_SELF()`` * ``PyCell_GET()`` * ``PyCode_GetNumFree()`` * ``PyDict_GET_SIZE()`` * ``PyFunction_GET_ANNOTATIONS()`` * ``PyFunction_GET_CLOSURE()`` * ``PyFunction_GET_CODE()`` * ``PyFunction_GET_DEFAULTS()`` * ``PyFunction_GET_GLOBALS()`` * ``PyFunction_GET_KW_DEFAULTS()`` * ``PyFunction_GET_MODULE()`` * ``PyHeapType_GET_MEMBERS()`` * ``PyInstanceMethod_GET_FUNCTION()`` * ``PyList_GET_SIZE()`` * ``PyMemoryView_GET_BASE()`` * ``PyMemoryView_GET_BUFFER()`` * ``PyMethod_GET_FUNCTION()`` * ``PyMethod_GET_SELF()`` * ``PySet_GET_SIZE()`` * ``PyTuple_GET_SIZE()`` * ``PyUnicode_GET_DATA_SIZE()`` * ``PyUnicode_GET_LENGTH()`` * ``PyUnicode_GET_LENGTH()`` * ``PyUnicode_GET_SIZE()`` * ``PyWeakref_GET_OBJECT()`` "AS" macros ^^^^^^^^^^^ * ``PyByteArray_AS_STRING()`` * ``PyBytes_AS_STRING()`` * ``PyFloat_AS_DOUBLE()`` * ``PyUnicode_AS_DATA()`` * ``PyUnicode_AS_UNICODE()`` PyUnicode macros ^^^^^^^^^^^^^^^^ * ``PyUnicode_1BYTE_DATA()`` * ``PyUnicode_2BYTE_DATA()`` * ``PyUnicode_4BYTE_DATA()`` * ``PyUnicode_DATA()`` * ``PyUnicode_IS_ASCII()`` * ``PyUnicode_IS_COMPACT()`` * ``PyUnicode_IS_READY()`` * ``PyUnicode_KIND()`` * ``PyUnicode_READ()`` * ``PyUnicode_READ_CHAR()`` PyDateTime "GET" macros ^^^^^^^^^^^^^^^^^^^^^^^ * ``PyDateTime_DATE_GET_FOLD()`` * ``PyDateTime_DATE_GET_HOUR()`` * ``PyDateTime_DATE_GET_MICROSECOND()`` * ``PyDateTime_DATE_GET_MINUTE()`` * ``PyDateTime_DATE_GET_SECOND()`` * ``PyDateTime_DATE_GET_TZINFO()`` * ``PyDateTime_DELTA_GET_DAYS()`` * ``PyDateTime_DELTA_GET_MICROSECONDS()`` * ``PyDateTime_DELTA_GET_SECONDS()`` * ``PyDateTime_GET_DAY()`` * ``PyDateTime_GET_MONTH()`` * ``PyDateTime_GET_YEAR()`` * ``PyDateTime_TIME_GET_FOLD()`` * ``PyDateTime_TIME_GET_HOUR()`` * ``PyDateTime_TIME_GET_MICROSECOND()`` * ``PyDateTime_TIME_GET_MINUTE()`` * ``PyDateTime_TIME_GET_SECOND()`` * ``PyDateTime_TIME_GET_TZINFO()`` PyDescr macros ^^^^^^^^^^^^^^ * ``PyDescr_NAME()`` * ``PyDescr_TYPE()`` Port C extensions to Python 3.11 -------------------------------- In practice, the majority of projects affected by these PEP only have to make two changes: * Replace ``Py_TYPE(obj) = new_type;`` with ``Py_SET_TYPE(obj, new_type);``. * Replace ``Py_SIZE(obj) = new_size;`` with ``Py_SET_SIZE(obj, new_size);``. The `pythoncapi_compat project <https://github.com/pythoncapi/pythoncapi_compat>`_ can be used to update automatically C extensions: add Python 3.11 support without losing support with older Python versions. The project provides a header file which provides ``Py_SET_REFCNT()``, ``Py_SET_TYPE()`` and ``Py_SET_SIZE()`` functions to Python 3.8 and older. PyTuple_GET_ITEM() and PyList_GET_ITEM() ---------------------------------------- The ``PyTuple_GET_ITEM()`` and ``PyList_GET_ITEM()`` macros are left unchanged. The code pattern ``&PyTuple_GET_ITEM(tuple, 0)`` and ``&PyList_GET_ITEM(list, 0)`` is still commonly used to get access to the inner ``PyObject**`` array. Changing these macros is out of the scope of this PEP. Backwards Compatibility ======================= The proposed C API changes are backward incompatible on purpose. At December 1, 2021, a code search on the PyPI top 5000 projects (4760 projects in practice, others don't have a source archive) found that `only 14 projects are affected <https://bugs.python.org/issue45476#msg407456>`_ (0.3%): * datatable (1.0.0) * frozendict (2.1.1) * guppy3 (3.1.2) * M2Crypto (0.38.0) * mecab-python3 (1.0.4) * mypy (0.910) * Naked (0.1.31) * pickle5 (0.0.12) * pysha3 (1.0.2) * python-snappy (0.6.0) * recordclass (0.16.3) * scipy (1.7.3) * zodbpickle (2.2.0) * zstd (1.5.0.2) These 14 projects only use 4 macros as l-value: * ``PyDescr_NAME()`` and ``PyDescr_TYPE()`` (2 projects) * ``Py_SIZE()`` (8 projects) * ``Py_TYPE()`` (4 projects) Moreover, `24 projects just have to regenerate their Cython code <https://bugs.python.org/issue45476#msg407416>`_ to use ``Py_SET_TYPE()``. This change does not follow the PEP 387 deprecation process. There is no known way to emit a deprecation warning only when a macro is used as a l-value, but not when it's used differently (ex: as a r-value). Relationship with the HPy project ================================= The HPy project --------------- The hope with the HPy project is indeed to provide a C API that is close to the original API to make porting easy and have it perform as close to the existing API as possible. At the same time, HPy is sufficently removed to be a good "C extension API" (as opposed to a stable subset of the CPython implementation API) that does not leak implementation details. To ensure this latter property is why the HPy project tries to develop everything in parallel for CPython, PyPy, and GraalVM Python. HPy is still evolving very fast. Issues are still being solved while migrating NumPy, and work has begun on adding support for HPy to Cython. Work on pybind11 is starting soon. Tim Felgentreff believes by the time HPy has these users of the existing C API working, HPy should be in a state where it is generally useful and can be deemed stable enough that further development can follow a more stable process. In the long run the HPy project would like to become a promoted API to write Python C extensions. The HPy project is a good solution for the long term. It has the advantage of being developed outside Python and it doesn't require any C API change. The C API is here is stay for a few more years ---------------------------------------------- The first concern about HPy is that right now, HPy is not mature nor widely used, and CPython still has to continue supporting a large amount of C extensions which are not likely to be ported to HPy soon. The second concern is the inability to evolve CPython internals to implement new optimizations, and the inefficient implementation of the current C API in PyPy, GraalPython, etc. Sadly, HPy will only solve these problems when most C extensions will be fully ported to HPy: when it will become reasonable to consider dropping the "legacy" Python C API. While porting a C extension to HPy can be done incrementally on CPython, it requires to modify a lot of code and takes time. Porting most C extensions to HPy is expected to take a few years. This PEP proposes to make the C API "less bad" by fixing one problem which is clearily identified as causing practical issues: macros used as l-values. This PEP only requires to update a minority of C extensions, and usually only a few lines need to be changed in impacted extensions. For example, numpy 1.22 is made of 307,300 lines of C code, and adapting numpy to the this PEP only modified 11 lines (use Py_SET_TYPE and Py_SET_SIZE) and adding 4 lines (to define Py_SET_TYPE and Py_SET_SIZE for Python 3.8 and older). Porting numpy to HPy is expected to require modifying more lines than that. Right now, it's hard to bet which approach is the best: fixing the current C API, or focusing on HPy. It would be risky to only focus on HPy. Rejected Idea: Leave the macros as they are =========================================== The documentation of each function can discourage developers to use macros to modify Python objects. If these is a need to make an assignment, a setter function can be added and the macro documentation can require to use the setter function. For example, a ``Py_SET_TYPE()`` function has been added to Python 3.9 and the ``Py_TYPE()`` documentation now requires to use the ``Py_SET_TYPE()`` function to set an object type. If developers use macros as l-value, it's their responsibility when their code breaks, not the Python responsibility. We are operating under the consenting adults principle: we expect users of the Python C API to use it as documented and expect them to take care of the fallout, if things break when they don't. This idea was rejected because only few developers read the documentation, and only a minority is tracking changes of the Python C API documentation. The majority of developers are only using CPython and so are not aware of compatibility issues with other Python implementations. Moreover, continuing to allow using macros as l-value does not help the HPy project and leaves the burden of emulating them on GraalVM's Python implementation. Macros already modified ======================= The following C API macros have already been modified to disallow using them as l-value: * ``PyCell_SET()`` * ``PyList_SET_ITEM()`` * ``PyTuple_SET_ITEM()`` * ``Py_REFCNT()`` (Python 3.10): ``Py_SET_REFCNT()`` must be used * ``_PyGCHead_SET_FINALIZED()`` * ``_PyGCHead_SET_NEXT()`` * ``asdl_seq_GET()`` * ``asdl_seq_GET_UNTYPED()`` * ``asdl_seq_LEN()`` * ``asdl_seq_SET()`` * ``asdl_seq_SET_UNTYPED()`` For example, ``PyList_SET_ITEM(list, 0, item) < 0`` now fails with a compiler error as expected. Discussion ========== * `PEP 674: Disallow using macros as l-value <https://mail.python.org/archives/list/python-dev@python.org/thread/KPIJPPJ6…>`_ (Nov 30, 2021) References ========== * `Python C API: Add functions to access PyObject <https://vstinner.github.io/c-api-abstract-pyobject.html>`_ (October 2021) article by Victor Stinner * `[C API] Disallow using PyFloat_AS_DOUBLE() as l-value <https://bugs.python.org/issue45476>`_ (October 2021) * `[capi-sig] Py_TYPE() and Py_SIZE() become static inline functions <https://mail.python.org/archives/list/capi-sig@python.org/thread/WGRLTHTHC3…>`_ (September 2021) * `[C API] Avoid accessing PyObject and PyVarObject members directly: add Py_SET_TYPE() and Py_IS_TYPE(), disallow Py_TYPE(obj)=type <https://bugs.python.org/issue39573>`__ (February 2020) * `bpo-30459: PyList_SET_ITEM could be safer <https://bugs.python.org/issue30459>`_ (May 2017) Copyright ========= This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive.

3 7

Increase of Spammy PRs and PR reviews
by Lrupert Feb. 1, 2022

Feb. 1, 2022

As someone who is watching the python/cpython repository, I'm very used to see lots of traffic. But lately there have been a surge of spammy PRs which are about the same, generally very trivial subject but individually fixing each occurrence one by one: - Add coverage to X (tens of them, as separate PRs) - Make `test_xxx` executable with direct invocation (tens of them, as separate PRs) - Lint source with flake8, fix linting errors (stylistic changes) And lots of non-committer PR reviews that only approve. Am I the only one who feels like this is only done to 'grind' commits (get a higher number of commits into the repository, and boast about it)? In the past there were one or two people who would submit typo fixes, but most of them weren't making it continuously. The situation right now feels much worse than those.

21 29

PEP 651, Robust Stack Overflow Handling, Rejection notice
by Python Steering Council Jan. 31, 2022

Jan. 31, 2022

Hi Mark, Thank you for submitting PEP 651. The Steering Council has spent the past two weeks reviewing PEP 651. After careful consideration, we have decided to reject the PEP. The following were the key points that led us to this decision: * The benefits are not compelling enough. Deep recursion is not a common tool in Python, and even with PEP 651 it would not be efficient enough to make it a common tool. * The benefit of PEP 651 is negated as soon as a non-Python function is involved in the recursion, making the likelihood of it being useful even smaller. It also creates easy pitfalls for users who do end up relying on recursion. * We believe the PEP understates the disruption created by the technical solution of multiple Python stack frames per C call. Although this may be solvable, it will certainly cause substantial disruption to existing debuggers, tracers, and state inspection tools as they need to adapt to this change (which may not be trivial). * As the way to approach this will be platform-specific (as some parts of the proposal are not portable), this can cause generic Python code to behave differently on different platforms, making this kind of code less portable and less predictable. In the end, the benefit of the PEP does not outweigh the cost of the potential breakage, confusion, and unpredictability of the feature. With our appreciation, The Python Steering Council

6 8

Blocking the main branch due to too many buildbots failing
by Pablo Galindo Salgado Jan. 29, 2022

Jan. 29, 2022

Hi everyone, We have a huge amount of buildbots failing and seems to be related to different issues that keep piling up. To prevent this from going worse,* I am blocking the main branch* *until these issues are resolved.* Only release managers and the developer in residence will be able to merge pull requests until these issues are fixed. Please, ping me if you have a pull request for fixing any of these issues so we can merge. I apologize for the inconvenience. Thanks for your understanding, Regards from rainy London, Pablo Galindo Salgado

2 1

Summary of Python tracker Issues
by Python tracker Jan. 28, 2022

Jan. 28, 2022

ACTIVITY SUMMARY (2022-01-21 - 2022-01-28) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 7157 (-18) closed 51138 (+124) total 58295 (+106) Open issues with patches: 2888 Issues opened (71) ================== #33205: GROWTH_RATE prevents dict shrinking https://bugs.python.org/issue33205 reopened by rhettinger #38195: A bug in the multiprocessing module https://bugs.python.org/issue38195 reopened by eshkrig #44733: Feature request: maxtasksperchild for ProcessPoolExecutor https://bugs.python.org/issue44733 reopened by gregory.p.smith #44734: turtle: tests for Vec2D.__abs__ are too strict https://bugs.python.org/issue44734 reopened by petr.viktorin #45162: Remove old deprecated unittest features https://bugs.python.org/issue45162 reopened by gregory.p.smith #45200: Address Sanitizer: libasan dead lock in pthread_create() (test https://bugs.python.org/issue45200 reopened by vstinner #45680: Documentation on `GenericAlias` objects and `__class_getitem__ https://bugs.python.org/issue45680 reopened by kj #46240: Incorrect hint about forgetting a comma https://bugs.python.org/issue46240 reopened by vstinner #46285: protocol_version in http.server.test can be ignored https://bugs.python.org/issue46285 reopened by eric.araujo #46462: Email Header Folding Converts Non-CRLF Newlines to CRLFs https://bugs.python.org/issue46462 opened by jwalterclark #46464: concurrent.futures.ProcessPoolExecutor can deadlock when tcmal https://bugs.python.org/issue46464 opened by yilei #46465: Regression caused by CALL_FUNCTION specialization for C functi https://bugs.python.org/issue46465 opened by vstinner #46472: A option that choose between single quote and double quote in https://bugs.python.org/issue46472 opened by I-love-study #46475: typing.Never and typing.assert_never https://bugs.python.org/issue46475 opened by Jelle Zijlstra #46477: Enum: ensure bitwise operators on subclasses are correct https://bugs.python.org/issue46477 opened by ethan.furman #46479: Implement typing.reveal_locals https://bugs.python.org/issue46479 opened by Jelle Zijlstra #46480: Implement typing.assert_type https://bugs.python.org/issue46480 opened by Jelle Zijlstra #46482: `typing.Annotation.__new__` is not covered https://bugs.python.org/issue46482 opened by sobolevn #46483: `pathlib.PurePath.__class_getitem__` does not return `GenericA https://bugs.python.org/issue46483 opened by sobolevn #46484: Add test for Calendar().iterweekdays() https://bugs.python.org/issue46484 opened by wangjiahua #46487: `_SSLProtocolTransport` doesn't have the `get_write_buffer_lim https://bugs.python.org/issue46487 opened by mooncell07 #46489: webbrowser crashes Ubuntu kernel https://bugs.python.org/issue46489 opened by dizcza #46490: Add "follow_symlinks=False" support for "os.utime()" on Window https://bugs.python.org/issue46490 opened by Delgan #46493: Add an API to indicate if the process might have multiple thre https://bugs.python.org/issue46493 opened by gregory.p.smith #46494: Mention typing_extensions in the typing documentation https://bugs.python.org/issue46494 opened by Jelle Zijlstra #46495: IDLE subsection of What's New 3.11 https://bugs.python.org/issue46495 opened by terry.reedy #46496: idlelib/NEWS.txt for 3.11.0 and backports https://bugs.python.org/issue46496 opened by terry.reedy #46497: IDLE macOS shortcut ctrl+S doesn��t work for show completions https://bugs.python.org/issue46497 opened by dvd101x #46498: Add new triplets for loongarch64 https://bugs.python.org/issue46498 opened by loongson-zn #46500: make timeit module accept files https://bugs.python.org/issue46500 opened by CCLDArjun #46501: Windows 10, turtle left right not working https://bugs.python.org/issue46501 opened by wizprokidz #46506: [Windows] wrap CreateFile to support follow_symlinks https://bugs.python.org/issue46506 opened by eryksun #46507: enabling cProfile to profile code given as an argument "�� la" https://bugs.python.org/issue46507 opened by jul2 #46508: codec name acceptance became way too lenient in 3.9 https://bugs.python.org/issue46508 opened by gregory.p.smith #46509: Type-specialized Py_DECREF https://bugs.python.org/issue46509 opened by Dennis Sweeney #46511: dataclasses: Allow typing.Annotated to wrap dataclasses-specif https://bugs.python.org/issue46511 opened by GBeauregard #46512: Explicit or correct behavior of filecmp.cmpfiles w/ absolute p https://bugs.python.org/issue46512 opened by bers #46518: SSL socket timeout not set after client connects via accept https://bugs.python.org/issue46518 opened by tomazas #46520: `ast.unparse` produces syntactically illegal code for identifi https://bugs.python.org/issue46520 opened by Kodiologist #46521: compile_command not raising syntax error when command ends wit https://bugs.python.org/issue46521 opened by tusharsadhwani #46522: concurrent.futures.__getattr__ raises the wrong AttributeError https://bugs.python.org/issue46522 opened by graingert #46523: Test suite skips failing tests when setUp[Class] fails https://bugs.python.org/issue46523 opened by sobolevn #46524: test_peg_generator takes 8 minutes on Windows https://bugs.python.org/issue46524 opened by vstinner #46525: datetime.timestamp() lose precision when the time is too large https://bugs.python.org/issue46525 opened by yilei #46526: iglob exclude patterns https://bugs.python.org/issue46526 opened by hleth #46528: Simplify the VM's stack manipulations https://bugs.python.org/issue46528 opened by brandtbucher #46532: Improve effeciency of PRECALL/CALL instructions https://bugs.python.org/issue46532 opened by Mark.Shannon #46533: Specialize for staticmethods and classmethods https://bugs.python.org/issue46533 opened by Mark.Shannon #46534: Implementing PEP 673 (Self type) https://bugs.python.org/issue46534 opened by Gobot1234 #46535: Possible bug: pdb causes exception https://bugs.python.org/issue46535 opened by cklb #46540: dylibs not loading properly from NFS mounts https://bugs.python.org/issue46540 opened by embassy_vfx #46541: Replace _Py_IDENTIFIER() with statically initialized objects. https://bugs.python.org/issue46541 opened by eric.snow #46542: test_json and test_lib2to3 crash on s390x Fedora Clang 3.x bui https://bugs.python.org/issue46542 opened by vstinner #46543: Add sys._getfunc https://bugs.python.org/issue46543 opened by Jelle Zijlstra #46544: `textwrap.TextWrapper` leaks two intermediate vars into class https://bugs.python.org/issue46544 opened by sobolevn #46547: `pydoc.Helper` leaks several `for` loop variables https://bugs.python.org/issue46547 opened by sobolevn #46548: macOS installers cannot be signed on Monterey https://bugs.python.org/issue46548 opened by nneonneo #46550: __slots__ updates despite being read-only https://bugs.python.org/issue46550 opened by IanLee1521 #46553: typing: get_type_hints on stringified lone ClassVar raises Typ https://bugs.python.org/issue46553 opened by GBeauregard #46554: Add append keyword argument to Path.write_text() and Path.writ https://bugs.python.org/issue46554 opened by keelung-yang #46555: Unicode-mangled names refer inconsistently to constants https://bugs.python.org/issue46555 opened by Kodiologist #46556: pathlib.Path.__enter__() should emit DeprecationWarning https://bugs.python.org/issue46556 opened by barneygale #46557: Logging captured warnings with a format string unnecessarily g https://bugs.python.org/issue46557 opened by mnito #46559: base64 documentation is out-dated; altchars has to have the ex https://bugs.python.org/issue46559 opened by ynn #46560: ParamSpec: Typo in doc string https://bugs.python.org/issue46560 opened by ESchalton #46561: Descriptor resolution should own arguments passed to descripto https://bugs.python.org/issue46561 opened by tekknolagi #46563: Add tests and documentation regarding context of exception in https://bugs.python.org/issue46563 opened by iritkatriel #46564: Near zero-cost super().meth() calls via adaptive superinstruct https://bugs.python.org/issue46564 opened by kj #46565: Multiple modules leak `for` loop variables into module's names https://bugs.python.org/issue46565 opened by sobolevn #46566: Support -3.11-arm64 in py.exe launcher https://bugs.python.org/issue46566 opened by steve.dower #46567: Add Tcl/Tk builds for ARM64 https://bugs.python.org/issue46567 opened by steve.dower Most recent 15 issues with no replies (15) ========================================== #46567: Add Tcl/Tk builds for ARM64 https://bugs.python.org/issue46567 #46566: Support -3.11-arm64 in py.exe launcher https://bugs.python.org/issue46566 #46564: Near zero-cost super().meth() calls via adaptive superinstruct https://bugs.python.org/issue46564 #46563: Add tests and documentation regarding context of exception in https://bugs.python.org/issue46563 #46559: base64 documentation is out-dated; altchars has to have the ex https://bugs.python.org/issue46559 #46556: pathlib.Path.__enter__() should emit DeprecationWarning https://bugs.python.org/issue46556 #46555: Unicode-mangled names refer inconsistently to constants https://bugs.python.org/issue46555 #46547: `pydoc.Helper` leaks several `for` loop variables https://bugs.python.org/issue46547 #46543: Add sys._getfunc https://bugs.python.org/issue46543 #46540: dylibs not loading properly from NFS mounts https://bugs.python.org/issue46540 #46535: Possible bug: pdb causes exception https://bugs.python.org/issue46535 #46534: Implementing PEP 673 (Self type) https://bugs.python.org/issue46534 #46525: datetime.timestamp() lose precision when the time is too large https://bugs.python.org/issue46525 #46518: SSL socket timeout not set after client connects via accept https://bugs.python.org/issue46518 #46512: Explicit or correct behavior of filecmp.cmpfiles w/ absolute p https://bugs.python.org/issue46512 Most recent 15 issues waiting for review (15) ============================================= #46565: Multiple modules leak `for` loop variables into module's names https://bugs.python.org/issue46565 #46564: Near zero-cost super().meth() calls via adaptive superinstruct https://bugs.python.org/issue46564 #46563: Add tests and documentation regarding context of exception in https://bugs.python.org/issue46563 #46561: Descriptor resolution should own arguments passed to descripto https://bugs.python.org/issue46561 #46560: ParamSpec: Typo in doc string https://bugs.python.org/issue46560 #46557: Logging captured warnings with a format string unnecessarily g https://bugs.python.org/issue46557 #46556: pathlib.Path.__enter__() should emit DeprecationWarning https://bugs.python.org/issue46556 #46554: Add append keyword argument to Path.write_text() and Path.writ https://bugs.python.org/issue46554 #46553: typing: get_type_hints on stringified lone ClassVar raises Typ https://bugs.python.org/issue46553 #46547: `pydoc.Helper` leaks several `for` loop variables https://bugs.python.org/issue46547 #46544: `textwrap.TextWrapper` leaks two intermediate vars into class https://bugs.python.org/issue46544 #46543: Add sys._getfunc https://bugs.python.org/issue46543 #46542: test_json and test_lib2to3 crash on s390x Fedora Clang 3.x bui https://bugs.python.org/issue46542 #46541: Replace _Py_IDENTIFIER() with statically initialized objects. https://bugs.python.org/issue46541 #46534: Implementing PEP 673 (Self type) https://bugs.python.org/issue46534 Top 10 most discussed issues (10) ================================= #45382: platform() is not able to detect windows 11 https://bugs.python.org/issue45382 17 msgs #46465: Regression caused by CALL_FUNCTION specialization for C functi https://bugs.python.org/issue46465 13 msgs #41370: PEP 585 and ForwardRef https://bugs.python.org/issue41370 9 msgs #46528: Simplify the VM's stack manipulations https://bugs.python.org/issue46528 9 msgs #46553: typing: get_type_hints on stringified lone ClassVar raises Typ https://bugs.python.org/issue46553 9 msgs #46425: Multiple test modules fail to run if invoked directly https://bugs.python.org/issue46425 8 msgs #46524: test_peg_generator takes 8 minutes on Windows https://bugs.python.org/issue46524 8 msgs #34680: asyncio event_loop fails when accessed from multiple threads https://bugs.python.org/issue34680 7 msgs #38472: setup.py: GCC detection is broken when cross-compiling with a https://bugs.python.org/issue38472 7 msgs #45476: [C API] PEP 674: Disallow using macros (Py_TYPE and Py_SIZE) a https://bugs.python.org/issue45476 7 msgs Issues closed (125) =================== #5884: pydoc to return error status code https://bugs.python.org/issue5884 closed by iritkatriel #7057: tkinter doc: more 3.x updates https://bugs.python.org/issue7057 closed by zach.ware #10943: abitype: Need better support to port C extension modules to th https://bugs.python.org/issue10943 closed by zach.ware #21987: TarFile.getmember on directory requires trailing slash iff ove https://bugs.python.org/issue21987 closed by serhiy.storchaka #22045: Python make issue https://bugs.python.org/issue22045 closed by iritkatriel #22211: Remove VMS specific code in expat.h & xmlrole.h https://bugs.python.org/issue22211 closed by iritkatriel #23289: concurrent.futures.Executor.map is not equivalent to map. https://bugs.python.org/issue23289 closed by iritkatriel #23556: [doc] Scope for raise without argument is different in Python https://bugs.python.org/issue23556 closed by iritkatriel #23769: valgrind reports leaks for test_zipimport https://bugs.python.org/issue23769 closed by vstinner #24046: Incomplete build on AIX https://bugs.python.org/issue24046 closed by iritkatriel #29844: Windows Python installers not installing DLL to System32/SysWO https://bugs.python.org/issue29844 closed by zach.ware #30053: Problems building with --enable-profiling on macOS using homeb https://bugs.python.org/issue30053 closed by iritkatriel #30424: make pydoc-topics fails https://bugs.python.org/issue30424 closed by iritkatriel #31011: Users (except from the one who installed) not able to see pyt https://bugs.python.org/issue31011 closed by iritkatriel #31305: 'pydoc -w import' report "no Python documentation found for 'i https://bugs.python.org/issue31305 closed by iritkatriel #31698: Add REQ_NAME to the node.h API https://bugs.python.org/issue31698 closed by Jelle Zijlstra #31991: Race condition in wait with timeout for multiprocessing.Event https://bugs.python.org/issue31991 closed by iritkatriel #32202: [ctypes] all long double tests fail on android-24-x86_64 https://bugs.python.org/issue32202 closed by iritkatriel #32203: [ctypes] test_struct_by_value fails on android-24-arm64 https://bugs.python.org/issue32203 closed by iritkatriel #32343: Leak Sanitizer reports memory leaks while building using ASAN https://bugs.python.org/issue32343 closed by iritkatriel #33822: IDLE subsection of What's New 3.8 https://bugs.python.org/issue33822 closed by terry.reedy #33936: OPENSSL_VERSION_1_1 never defined in _hashopenssl.c https://bugs.python.org/issue33936 closed by christian.heimes #33983: unify types for lib2to3.pytree.Base.children https://bugs.python.org/issue33983 closed by Jelle Zijlstra #35774: ASAN, memory leak https://bugs.python.org/issue35774 closed by vstinner #36257: configure with --with-icc --with-cxx-main=icpc https://bugs.python.org/issue36257 closed by iritkatriel #37080: Cannot compile Python3.7.3 on Alt-F (ARM) https://bugs.python.org/issue37080 closed by iritkatriel #37886: PyStructSequence_UnnamedField not exported https://bugs.python.org/issue37886 closed by iritkatriel #38039: Segfault when pickling dictionary with large pandas dataframes https://bugs.python.org/issue38039 closed by iritkatriel #38665: Crash when running SQLAlchemy with pyodbc https://bugs.python.org/issue38665 closed by iritkatriel #39708: final link stage in compile fails for 3.8.1 with missing CFLAG https://bugs.python.org/issue39708 closed by iritkatriel #39731: ModuleNotFoundError: No module named '_ctypes' https://bugs.python.org/issue39731 closed by iritkatriel #39854: f-strings with format specifiers have wrong col_offset https://bugs.python.org/issue39854 closed by iritkatriel #40170: [C API] Prepare PyTypeObject structure for a stable ABI: avoid https://bugs.python.org/issue40170 closed by vstinner #40250: unable to comment out r'\u' string with triple quote marks https://bugs.python.org/issue40250 closed by iritkatriel #40356: OverflowError: mktime argument out of range https://bugs.python.org/issue40356 closed by iritkatriel #41209: Scripts Folder is Empty https://bugs.python.org/issue41209 closed by iritkatriel #41403: Uncaught AttributeError in unittest.mock._get_target https://bugs.python.org/issue41403 closed by iritkatriel #41603: Compilation issue 3.8.5 with Redhat 7.8 and gcc version 4.8.5 https://bugs.python.org/issue41603 closed by iritkatriel #41682: [Windows] : Proactor test_sendfile_close_peer_in_the_middle_of https://bugs.python.org/issue41682 closed by vstinner #41906: logging.config.dictConfig does not work with callable filters https://bugs.python.org/issue41906 closed by vinay.sajip #42091: strftime returns empty string for -d, -I 3.8.3 https://bugs.python.org/issue42091 closed by iritkatriel #42585: Segmentation fault on Linux with multiprocess queue https://bugs.python.org/issue42585 closed by iritkatriel #42982: Update suggested number of iterations for pbkdf2_hmac() https://bugs.python.org/issue42982 closed by gregory.p.smith #43536: 3.9.2 --without-pymalloc --with-pydebug --with-valgrind: test https://bugs.python.org/issue43536 closed by vstinner #44642: Union of a type and the typing module function https://bugs.python.org/issue44642 closed by sobolevn #45578: Missing tests for the dis module https://bugs.python.org/issue45578 closed by taleinat #45868: xattr support missing in os module under cygwin https://bugs.python.org/issue45868 closed by iritkatriel #45945: compileall.py throws a traceback when using -j0 and thus 'make https://bugs.python.org/issue45945 closed by iritkatriel #46071: Graphlib documentation (edge direction) https://bugs.python.org/issue46071 closed by dam1784 #46091: IndendationError from multi-line indented statements https://bugs.python.org/issue46091 closed by pablogsal #46098: Missing test for multi-line errors in traceback https://bugs.python.org/issue46098 closed by iritkatriel #46124: Deprecation warning in zoneinfo module https://bugs.python.org/issue46124 closed by jaraco #46157: Typo in JSON documentation https://bugs.python.org/issue46157 closed by serhiy.storchaka #46204: Graphlib documentation (general cleanup) https://bugs.python.org/issue46204 closed by dam1784 #46214: Remove unused opcode ROT_FOUR https://bugs.python.org/issue46214 closed by iritkatriel #46249: [sqlite3] move set lastrowid out of the query loop and enable https://bugs.python.org/issue46249 closed by corona10 #46254: Better fitting type for iterating in the trace_init C function https://bugs.python.org/issue46254 closed by iritkatriel #46340: DeprecationWarning emitted when running asyncio tests https://bugs.python.org/issue46340 closed by kumaraditya303 #46378: Experiment with LLVM BOLT binary optimizer https://bugs.python.org/issue46378 closed by corona10 #46383: _zoneinfo module_free has invalid function signature https://bugs.python.org/issue46383 closed by christian.heimes #46396: `Concatenate` should not raise any semantic errors https://bugs.python.org/issue46396 closed by gvanrossum #46399: Addition of `mapping` attribute to dict views classes has inad https://bugs.python.org/issue46399 closed by AlexWaygood #46406: optimize int division https://bugs.python.org/issue46406 closed by mark.dickinson #46407: optimizing `1 << n` or `2 ** n` and modulo-only operations https://bugs.python.org/issue46407 closed by tim.peters #46416: Direct invocation of `Lib/test/test_typing.py` fails https://bugs.python.org/issue46416 closed by sobolevn #46417: Clear static types in Py_Finalize() for embedded Python https://bugs.python.org/issue46417 closed by vstinner #46419: Incomplete Comparison to C++ Methods https://bugs.python.org/issue46419 closed by gvanrossum #46420: Use NOTRACE_DISPATCH in specialized opcodes https://bugs.python.org/issue46420 closed by Dennis Sweeney #46422: Why do we need `dis.Positions`? https://bugs.python.org/issue46422 closed by sobolevn #46426: Improve tests for the dir_fd argument https://bugs.python.org/issue46426 closed by serhiy.storchaka #46429: Merge all deepfrozen files into one https://bugs.python.org/issue46429 closed by kumaraditya303 #46431: Trouble subclassing ExceptionGroup https://bugs.python.org/issue46431 closed by iritkatriel #46434: pdb help fails with AttributeError when using Windows embeddab https://bugs.python.org/issue46434 closed by steve.dower #46442: testExceptionCleanupNames doesn't test anything? https://bugs.python.org/issue46442 closed by eric.smith #46445: Multiple inheritance of TypedDict is not covered in `test_typi https://bugs.python.org/issue46445 closed by sobolevn #46449: Deep-freezed modules create inconsistency in sys.gettotalrefco https://bugs.python.org/issue46449 closed by vstinner #46452: Possible false detection of Windows LZMA library as a malware https://bugs.python.org/issue46452 closed by terry.reedy #46453: argparse subparser help text is not escaped before string form https://bugs.python.org/issue46453 closed by iritkatriel #46460: Doc/library/dis.rst lists `versionchange` twice for `WITH_EXCE https://bugs.python.org/issue46460 closed by iritkatriel #46463: escape4chm.py script causing AttributeError in docs build https://bugs.python.org/issue46463 closed by steve.dower #46466: help function reads comments https://bugs.python.org/issue46466 closed by steven.daprano #46467: Rounding 5,50,500 behaves differently depending on preceding v https://bugs.python.org/issue46467 closed by steven.daprano #46468: http.server documentation missing default value for port https://bugs.python.org/issue46468 closed by asvetlov #46469: asyncio Generic classes should return GenericAlias in __class_ https://bugs.python.org/issue46469 closed by asvetlov #46470: `_remove_dups_flatten` in `typing.py` contains dead branch https://bugs.python.org/issue46470 closed by kj #46471: use global singletons for single byte bytes objects in deepfre https://bugs.python.org/issue46471 closed by erlendaasland #46473: importlib.metadata does not honor .egg-link files https://bugs.python.org/issue46473 closed by onlinespending #46474: Inefficient regular expression complexity in EntryPoint.patter https://bugs.python.org/issue46474 closed by jaraco #46476: Not all memory allocated by _Py_Quicken() is released at Pytho https://bugs.python.org/issue46476 closed by vstinner #46478: DirEntry.stat() of os.scandir() has no dir_fd parameter https://bugs.python.org/issue46478 closed by vstinner #46481: Implement vectorcall protocol for weakref_call() https://bugs.python.org/issue46481 closed by corona10 #46485: ~ PEG operator in the grammar https://bugs.python.org/issue46485 closed by pablogsal #46486: Rename DesciptorClassification => DescriptorClassification in https://bugs.python.org/issue46486 closed by rhettinger #46488: listsort.txt wrongly assumes you cannot calculate leading zero https://bugs.python.org/issue46488 closed by rhettinger #46491: typing: allow Annotated in outermost scope https://bugs.python.org/issue46491 closed by kj #46492: BrokenPipeError when piping to head (linux) https://bugs.python.org/issue46492 closed by royroy #46499: circular impoty https://bugs.python.org/issue46499 closed by iritkatriel #46502: Py_CompileString no longer allows to tell "incomplete input" f https://bugs.python.org/issue46502 closed by pablogsal #46503: assertion failure in Parser/string_parser.c https://bugs.python.org/issue46503 closed by eric.smith #46504: Faster code for trial quotient in x_divrem https://bugs.python.org/issue46504 closed by tim.peters #46505: Simplify exception handling code in py_compile https://bugs.python.org/issue46505 closed by iritkatriel #46510: Update Python2-style exception handling https://bugs.python.org/issue46510 closed by iritkatriel #46513: AC_C_CHAR_UNSIGNED from configure.ac confuses GCC 12+ by defin https://bugs.python.org/issue46513 closed by christian.heimes #46514: Pathlib Path.touch() seems to ignore groups write bit for mode https://bugs.python.org/issue46514 closed by ronaldoussoren #46515: SPAM https://bugs.python.org/issue46515 closed by mrabarnett #46516: Use existing unbound_local_error label in DELETE_FAST opcode https://bugs.python.org/issue46516 closed by kj #46517: Review exception handling in urllib https://bugs.python.org/issue46517 closed by iritkatriel #46519: test_typing failing on branch 3.10 https://bugs.python.org/issue46519 closed by kj #46527: enumerate no longer accepts iterable keyword argument https://bugs.python.org/issue46527 closed by corona10 #46529: Improve test coverage of `Union` and `Optional` repr() https://bugs.python.org/issue46529 closed by kj #46530: `'thread_time'` is missing from `test_get_clock_info` https://bugs.python.org/issue46530 closed by sobolevn #46531: Simplify exception handling in `doctest.py` https://bugs.python.org/issue46531 closed by sobolevn #46536: Better for loop https://bugs.python.org/issue46536 closed by eric.smith #46537: zipfile crash on windows, detected during pip install pyodbc- https://bugs.python.org/issue46537 closed by Martin-Forster #46538: [C API] Make the PyDescrObject structure opaque: PyDescr_NAME( https://bugs.python.org/issue46538 closed by vstinner #46539: typing: forward references don't understand special type forms https://bugs.python.org/issue46539 closed by AlexWaygood #46545: `textwrap.TextWrapper` leaks two intermediate vars into class https://bugs.python.org/issue46545 closed by sobolevn #46546: `importlib.metadata.DeprecatedList` leaks `method_name` variab https://bugs.python.org/issue46546 closed by sobolevn #46549: Error in list comprehension conditionals when used in class at https://bugs.python.org/issue46549 closed by Dennis Sweeney #46551: Provide number of workers option for fast PGO build time https://bugs.python.org/issue46551 closed by corona10 #46552: typing: get_type_hints can't handle stringified annotations wi https://bugs.python.org/issue46552 closed by gvanrossum #46558: Quadratic time internal base conversions https://bugs.python.org/issue46558 closed by tim.peters #46562: Add typeof or enum behavior in the typing module https://bugs.python.org/issue46562 closed by Jelle Zijlstra #1635741: Py_Finalize() doesn't clear all Python objects at exit https://bugs.python.org/issue1635741 closed by vstinner #1471934: Python libcrypt build problem on Solaris 8, 9, 10 and OpenSola https://bugs.python.org/issue1471934 closed by iritkatriel

1 0

Request to revert unittest and configparser incompatible changes in Python 3.11
by Victor Stinner Jan. 28, 2022

Jan. 28, 2022

Hi, My colleagues Tomáš Hrnčiar and Miro Hrončok made good progress on updating Python 3.10 to Python 3.11 in Fedora, but some specific Python 3.11 incompatible changes are causing more troubles than others: https://discuss.python.org/t/experience-with-python-3-11-in-fedora/12911 We propose to revert the following 2 changes in Python 3.11 and postpone them in a later Python version, once most projects will be compatible with these changes: * Removal of unittest aliases (bpo-45162): it broke 61 Fedora packages * Removals from configparser module (bpo-45173) - broke 28 Fedora packages -- We reported the issue to many affected projects, or when possible, we also wrote a pull request to make the code compatible (lot of those were made by others, e.g. Hugo van Kemenade, thank you!). The problem is that fixing a Fedora package requires multiple steps: * (1) Propose a pull request upstream * (2) Get the pull request merged upstream * (3) Wait for a new release upstream * (4) Update the Fedora package downstream, or backport the change in Fedora (only needed by Fedora) Identifying the Python incompatible changes causing most troubles took us a lot of time, but we did this work. Reverting the two Python 3.11 incompatible changes (causing most troubles) will save us "bug triage" time, to get more time on updating projects to Python 3.11 for the other remaining incompatible changes. We are not saying that these incompatible changes are bad, it's just a matter of getting most projects ready before Python 3.11 final will be released. -- By the way, before making a change known to be incompatible, it would be nice to run a code search on PyPI top 5000 projects to estimate how many projects will be broken, and try to update these projects *before* making the change. For example, only introduce an incompatible change into Python once less than 15 projects are affected. Getting a pull request merged is nice, but a release including the fix is way better for practical reasons: people use "pip install <project name>". -- Fedora work on Python 3.11 is public and tracked at: https://bugzilla.redhat.com/show_bug.cgi?id=PYTHON3.11 Click on "depends on" to see current issues: https://bugzilla.redhat.com/buglist.cgi?bug_id=2016048&bug_id_type=anddepen… Example of bz #2025600: mom fails to build with Python 3.11: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Victor Stinner -- in the name of the Python Red Hat / Fedora maintenance team -- Night gathers, and now my watch begins. It shall not end until my death.

12 16