Mishandled _POSIX_C_SOURCE and _XOPEN_SOURCE in pyconfig.h
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by examining pyconfig.h and the handling of _POSIX_C_SOURCE and _XOPEN_SOURCE described in the issue. Review the linked BPO issue and its discussion for the expected behavior, then identify an existing compile check or test entry point. Done means the macros are handled correctly across the affected Python 3.9–3.11 configurations.
Written by the indexing model from the issue text.
Description
| BPO | 17120 |
|---|---|
| Nosy | @loewis, @vstinner, @koobs, @iritkatriel |
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 2013-02-04.05:39:07.814>
labels = ['build', 'library', '3.9', '3.10', '3.11']
title = 'Mishandled _POSIX_C_SOURCE and _XOPEN_SOURCE in pyconfig.h'
updated_at = <Date 2021-12-12.19:07:28.318>
user = 'https://bugs.python.org/RAW'
bugs.python.org fields:
activity = <Date 2021-12-12.19:07:28.318>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-04.05:39:07.814>
creator = 'RAW'
dependencies = []
files = []
hgrepos = []
issue_num = 17120
keywords = []
message_count = 8.0
messages = ['181309', '183910', '185248', '226849', '241328', '400445', '400563', '400614']
nosy_count = 5.0
nosy_names = ['loewis', 'vstinner', 'koobs', 'RAW', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue17120'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PolicyEngine/policyengine-us#9559 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
from:qa priority:P2 reliability tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spec-kitty/spec-kitty#4874 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100