Case mismatch between "include" and "Include"
Open
Nobody has claimed this yet.
3.10
OS-windows
topic-installation
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41669 |
|---|---|
| Nosy | @pfmoore, @tjguk, @merwok, @zware, @zooba, @indygreg |
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-08-30.21:48:06.267>
labels = ['type-bug', '3.10', 'OS-windows']
title = 'Case mismatch between "include" and "Include"'
updated_at = <Date 2020-10-22.20:44:59.869>
user = 'https://github.com/indygreg'
bugs.python.org fields:
activity = <Date 2020-10-22.20:44:59.869>
actor = 'eric.araujo'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2020-08-30.21:48:06.267>
creator = 'indygreg'
dependencies = []
files = []
hgrepos = []
issue_num = 41669
keywords = []
message_count = 3.0
messages = ['376131', '376172', '379344']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'eric.araujo', 'zach.ware', 'steve.dower', 'indygreg']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41669'
versions = ['Python 3.10']
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
The payload names no source file, test, or entry point; start by reproducing the case mismatch on Windows and locating the affected include/Include references. Done means the reported casing inconsistency is resolved and the relevant behavior has regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100