pkgutil.walk_packages jumps out from given path if there is package with the same name in sys.path
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36053 |
|---|---|
| Nosy | @ncoghlan, @ekiro |
| PRs |
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 2019-02-20.16:37:07.621>
labels = ['3.8', 'type-bug', 'library']
title = 'pkgutil.walk_packages jumps out from given path if there is package with the same name in sys.path'
updated_at = <Date 2019-07-24.12:03:00.550>
user = 'https://github.com/ekiro'
bugs.python.org fields:
activity = <Date 2019-07-24.12:03:00.550>
actor = 'karkucik'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-02-20.16:37:07.621>
creator = 'karkucik'
dependencies = []
files = []
hgrepos = []
issue_num = 36053
keywords = ['patch']
message_count = 6.0
messages = ['336111', '339028', '339573', '339603', '343747', '348381']
nosy_count = 2.0
nosy_names = ['ncoghlan', 'karkucik']
pr_nums = ['11956']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36053'
versions = ['Python 3.8']
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 with the pkgutil.walk_packages entry point and the migrated BPO issue, then review the existing python/cpython#11956 patch and its discussion. Done means the package walk remains within the supplied path even when sys.path contains a package with the same name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100