Name collisions in pythoncore, preventing unity/jumbo build
Open
Nobody has claimed this yet.
3.9 (EOL)
build
interpreter-core
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40161 |
|---|---|
| Nosy | @ariccio |
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-04-02.22:14:07.199>
labels = ['interpreter-core', 'build', '3.9']
title = 'Name collisions in pythoncore, preventing unity/jumbo build'
updated_at = <Date 2020-04-02.22:14:07.199>
user = 'https://github.com/ariccio'
bugs.python.org fields:
activity = <Date 2020-04-02.22:14:07.199>
actor = 'Alexander Riccio'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-04-02.22:14:07.199>
creator = 'Alexander Riccio'
dependencies = []
files = []
hgrepos = []
issue_num = 40161
keywords = []
message_count = 1.0
messages = ['365636']
nosy_count = 1.0
nosy_names = ['Alexander Riccio']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue40161'
versions = ['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
Start by reproducing the unity/jumbo build failure described in the issue and inspect the generated pythoncore compilation output for the colliding names. Done means identifying and resolving the collisions so the unity/jumbo build completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100