Simplify readline / editline detection
Open
Nobody has claimed this yet.
3.11
build
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 46100 |
|---|---|
| Nosy | @gpshead, @tiran, @erlend-aasland |
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 2021-12-16.12:37:48.134>
labels = ['type-feature', 'build', '3.11']
title = 'Simplify readline / editline detection'
updated_at = <Date 2021-12-19.22:56:12.450>
user = 'https://github.com/tiran'
bugs.python.org fields:
activity = <Date 2021-12-19.22:56:12.450>
actor = 'erlendaasland'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2021-12-16.12:37:48.134>
creator = 'christian.heimes'
dependencies = []
files = []
hgrepos = []
issue_num = 46100
keywords = []
message_count = 3.0
messages = ['408700', '408701', '408934']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'christian.heimes', 'erlendaasland']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46100'
versions = ['Python 3.11']
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 locating CPython's build configuration and detection logic for readline and editline. Read the existing handling and related build checks before deciding what can be simplified. Done means the detection is simpler while still correctly handling the supported readline/editline cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100