◐ Shell
clean mode source ↗

gh-71587: Drop local reference cache to `_strptime` module in `_datetime` by neonene · Pull Request #120224 · python/cpython

added 3 commits

June 7, 2024 20:58

erlend-aasland

neonene

Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>

ericsnowcurrently

@neonene

@neonene neonene changed the title gh-71587: Fix reference caching to _strptime module in _datetime gh-71587: Drop local reference cache to _strptime module in _datetime

Jun 7, 2024

kumaraditya303

ericsnowcurrently

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

Jun 12, 2024
…_datetime` (pythongh-120224)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).
(cherry picked from commit 127c1d2)

Co-authored-by: neonene <53406459+neonene@users.noreply.github.com>

ericsnowcurrently pushed a commit that referenced this pull request

Jun 12, 2024
…`_datetime` (gh-120424)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).

(cherry picked from commit 127c1d2, AKA gh-120224)

Co-authored-by: neonene <53406459+neonene@users.noreply.github.com>

ericsnowcurrently pushed a commit that referenced this pull request

Jun 13, 2024
…`_datetime` (gh-120431)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).

(cherry picked from commit 127c1d2, AKA gh-120224)

mrahtz pushed a commit to mrahtz/cpython that referenced this pull request

Jun 30, 2024
…_datetime` (pythongh-120224)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).

noahbkim pushed a commit to hudson-trading/cpython that referenced this pull request

Jul 11, 2024
…_datetime` (pythongh-120224)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).

estyxx pushed a commit to estyxx/cpython that referenced this pull request

Jul 17, 2024
…_datetime` (pythongh-120224)

The _strptime module object was cached in a static local variable (in the datetime.strptime() implementation).  That's a problem when it crosses isolation boundaries, such as reinitializing the runtme or between interpreters.  This change fixes the problem by dropping the static variable, instead always relying on the normal sys.modules cache (via PyImport_Import()).