configured libdir not correctly passed to Python executable
Open
Nobody has claimed this yet.
3.10
3.11
3.12
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36758 |
|---|---|
| Nosy | @vstinner, @michael-o, @websurfer5 |
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-04-30.11:15:47.996>
labels = ['3.8', 'build', 'expert-installation']
title = 'configured libdir not correctly passed to Python executable'
updated_at = <Date 2019-12-10.07:51:18.677>
user = 'https://github.com/michael-o'
bugs.python.org fields:
activity = <Date 2019-12-10.07:51:18.677>
actor = 'xdegaye'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build', 'Installation']
creation = <Date 2019-04-30.11:15:47.996>
creator = 'michael-o'
dependencies = []
files = []
hgrepos = []
issue_num = 36758
keywords = []
message_count = 2.0
messages = ['341148', '341354']
nosy_count = 3.0
nosy_names = ['vstinner', 'michael-o', 'Jeffrey.Kintscher']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36758'
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 by tracing the Build/Installation path that passes the configured libdir to the Python executable; the issue names no files, tests, or entry points. Reproduce the reported configuration and identify where the libdir is lost or altered. Done means the configured libdir is correctly available to the Python executable and the behavior is covered by an appropriate test.
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