pyconfig.h is not placed in --includedir
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by reviewing the linked pyconfig-includedir.patch and the installation handling for --includedir. Confirm where pyconfig.h is generated and installed, then verify that it is placed in the configured include directory.
Written by the indexing model from the issue text.
Description
| BPO | 896330 |
|---|---|
| Nosy | @loewis, @tiran |
| Files |
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 2004-02-13.08:24:58.000>
labels = ['type-bug', 'expert-installation']
title = 'pyconfig.h is not placed in --includedir'
updated_at = <Date 2020-07-03.05:43:58.518>
user = 'https://bugs.python.org/goeran'
bugs.python.org fields:
activity = <Date 2020-07-03.05:43:58.518>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Installation']
creation = <Date 2004-02-13.08:24:58.000>
creator = 'goeran'
dependencies = []
files = ['36552']
hgrepos = []
issue_num = 896330
keywords = ['patch']
message_count = 8.0
messages = ['19983', '19984', '19985', '59177', '114322', '114420', '192579', '226448']
nosy_count = 5.0
nosy_names = ['loewis', 'goeran', 'morth', 'christian.heimes', 'lotheac']
pr_nums = []
priority = 'low'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue896330'
versions = ['Python 3.1', 'Python 2.7', 'Python 3.2', 'Python 3.3', 'Python 3.4', 'Python 3.5']
Linked PRs
- gh-141708
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100