Staging
v0.5.1
https://github.com/python/cpython
Revision d14775ddbb067bcfa6eca516d3cbe968a8c1334e authored by Pablo Galindo on 01 September 2020, 20:40:57 UTC, committed by GitHub on 01 September 2020, 20:40:57 UTC
When allocating MemoryError classes, there is some logic to use
pre-allocated instances in a freelist only if the type that is being
allocated is not a subclass of MemoryError. Unfortunately in the
destructor this logic is not present so the freelist is altered even
with subclasses of MemoryError..
(cherry picked from commit 9b648a95ccb4c3b14f1e87158f5c9f5dbb2f62c0)

Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
1 parent 4217b3c
Raw File
Tip revision: d14775ddbb067bcfa6eca516d3cbe968a8c1334e authored by Pablo Galindo on 01 September 2020, 20:40:57 UTC
[3.9] bpo-41654: Fix deallocator of MemoryError to account for subclasses (GH-22020) (GH-22045)
Tip revision: d14775d
CODE_OF_CONDUCT.md
# Code of Conduct

Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all the infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general, this means that everyone is expected to be **open**, **considerate**, and
**respectful** of others no matter what their position is within the project.

back to top