Regression in compileall ddir parameter when recursing
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38715 |
|---|---|
| Nosy | @serhiy-storchaka, @FFY00 |
| 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-11-06.07:12:13.431>
labels = ['3.7', '3.8', 'type-bug', 'library']
title = 'Regression in compileall ddir parameter when recursing'
updated_at = <Date 2020-05-03.17:15:40.122>
user = 'https://bugs.python.org/hetman'
bugs.python.org fields:
activity = <Date 2020-05-03.17:15:40.122>
actor = 'FFY00'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-06.07:12:13.431>
creator = 'hetman'
dependencies = []
files = []
hgrepos = []
issue_num = 38715
keywords = ['patch']
message_count = 3.0
messages = ['356102', '367984', '367986']
nosy_count = 3.0
nosy_names = ['serhiy.storchaka', 'hetman', 'FFY00']
pr_nums = ['17398']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38715'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7', '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 by reviewing the compileall entry point and the ddir parameter's behavior during recursive compilation. Check the historical pull request linked in the issue for context, then reproduce the regression and verify that recursive ddir handling matches the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100