Way working directory is added to sys.path differs between using -c or -m
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
docs
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42483 |
|---|---|
| Nosy | @vstinner, @plammens |
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-11-27.10:59:48.432>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9', 'docs']
title = 'Way working directory is added to sys.path differs between using -c or -m'
updated_at = <Date 2020-11-27.20:15:57.198>
user = 'https://github.com/plammens'
bugs.python.org fields:
activity = <Date 2020-11-27.20:15:57.198>
actor = 'plammens'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Interpreter Core']
creation = <Date 2020-11-27.10:59:48.432>
creator = 'plammens'
dependencies = []
files = []
hgrepos = []
issue_num = 42483
keywords = []
message_count = 3.0
messages = ['381942', '381960', '381963']
nosy_count = 3.0
nosy_names = ['vstinner', 'docs@python', 'plammens']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42483'
versions = ['Python 3.8', 'Python 3.9']
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 no source files or tests. Start by reproducing the difference in sys.path when Python is invoked with -c versus -m, then trace the command-line entry points that construct sys.path. Done means the behavior is made consistent or its documented difference is clearly specified, with regression coverage for both invocation forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100