importlib: lazy loading can result in reimporting a submodule
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
stdlib
topic-importlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39602 |
|---|---|
| Nosy | @brettcannon, @poxthegreat |
| Files |
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:
assignee = None
closed_at = None
created_at = <Date 2020-02-10.18:19:50.330>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'importlib: lazy loading can result in reimporting a submodule'
updated_at = <Date 2022-01-17.22:39:32.839>
user = 'https://github.com/poxthegreat'
bugs.python.org fields:
activity = <Date 2022-01-17.22:39:32.839>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-10.18:19:50.330>
creator = 'Pox TheGreat'
dependencies = []
files = ['48889']
hgrepos = []
issue_num = 39602
keywords = []
message_count = 1.0
messages = ['361705']
nosy_count = 2.0
nosy_names = ['brett.cannon', 'Pox TheGreat']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39602'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting and running the attached LazyImport.zip example, then trace the relevant importlib lazy-loading path. Confirm the behavior where a submodule is imported again, and use that reproduction to define completion as avoiding the reimport while retaining lazy loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100