Expose importlib._bootstrap._ModuleLockManager in importlib.machinery
Open
Nobody has claimed this yet.
stdlib
topic-importlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 30893 |
|---|---|
| Nosy | @brettcannon, @ncoghlan, @ericsnowcurrently |
| Dependencies |
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 2017-07-10.19:11:21.304>
labels = ['type-feature', 'library']
title = 'Expose importlib._bootstrap._ModuleLockManager in importlib.machinery'
updated_at = <Date 2017-07-11.01:22:17.177>
user = 'https://github.com/brettcannon'
bugs.python.org fields:
activity = <Date 2017-07-11.01:22:17.177>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-07-10.19:11:21.304>
creator = 'brett.cannon'
dependencies = ['30891']
files = []
hgrepos = []
issue_num = 30893
keywords = []
message_count = 2.0
messages = ['298077', '298098']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'ncoghlan', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30893'
versions = []
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 reading the importlib.machinery module and the internal importlib._bootstrap implementation of _ModuleLockManager. Check dependency bpo-30891 and existing importlib tests before deciding how the public exposure should be verified; done means the class is available through importlib.machinery with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100