-
-
Notifications
You must be signed in to change notification settings - Fork 34.4k
__lazy_import__ crashes with user-defined filters #144851
Copy link
Copy link
Closed
Labels
3.15new features, bugs and security fixesnew features, bugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)release-blockertype-crashA hard crash of the interpreter, possibly with a core dumpA hard crash of the interpreter, possibly with a core dump
Metadata
Metadata
Assignees
Labels
3.15new features, bugs and security fixesnew features, bugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)release-blockertype-crashA hard crash of the interpreter, possibly with a core dumpA hard crash of the interpreter, possibly with a core dump
Projects
Status
Done
Crash report
Bug description:
This crashes from an assertion error, only when
__lazy_import__is called directly:Moved from LazyImportsCabal#45 (couldn't have transferred it).
The compiler would always put a
LOAD_CONST (None)before anyIMPORT_NAMEfor imports withoutfrom, which is why this crash never happens in a regularlazy import.CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
__lazy_import__crash with user-defined filters #144852