Repository navigation
Use specs instead of just __loader__ in C code #86298
Copy link
Copy link
Closed
Labels
3.10 (EOL)end of lifeend of lifeinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)sprinttopic-importlibtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
_warnings.c, pylifecycle.c, and pythonrun.c all either use or set
__loader__but without also falling back on__spec__.- added3.10 (EOL)end of lifeend of lifeinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on Oct 23, 2020 I'm going to take a look at these module attribute issues during the 2022 core sprint.
I have
_warnings.cimplemented and tested.I think there's nothing to do for
pythonrun.c. These set__loader__but not__spec__directly, and the documentation outlines the expected semantics. If the documented semantics are incorrect, then there should be a separate tracking bug for that case.Looking at
pylifecycle.cnext.7 remaining items
- added a commit that references this issue
on May 20, 2024 These warnings are only emitted for the C implementation. See #122255.
- added 3 commits that reference this issue
on Jul 25, 2024
Metadata
Metadata
Assignees
Labels
3.10 (EOL)end of lifeend of lifeinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)sprinttopic-importlibtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Projects
- StatusShow more project fieldsDone
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
Linked PRs