[feature] runpy.run_module should mimic script launch behavior for sys.path
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-importlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31874 |
|---|---|
| Nosy | @jaraco, @ncoghlan |
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-10-26.14:01:14.693>
labels = ['3.7', 'type-feature', 'library']
title = '[feature] runpy.run_module should mimic script launch behavior for sys.path'
updated_at = <Date 2019-09-03.07:47:43.368>
user = 'https://github.com/jaraco'
bugs.python.org fields:
activity = <Date 2019-09-03.07:47:43.368>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-10-26.14:01:14.693>
creator = 'jaraco'
dependencies = []
files = []
hgrepos = []
issue_num = 31874
keywords = []
message_count = 4.0
messages = ['305054', '305057', '323419', '351070']
nosy_count = 2.0
nosy_names = ['jaraco', 'ncoghlan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31874'
versions = ['Python 3.7']
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
The issue names runpy.run_module and its expected relationship to script-launch sys.path behavior, but it does not name a file or test. Start by locating that entry point and comparing the two behaviors; done means runpy.run_module matches the intended script-launch sys.path semantics with focused regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100