What do "cased" and "uncased" mean?
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44175 |
|---|---|
| Nosy | @rhettinger, @MojoVampire, @akulakov |
| PRs |
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-05-19.03:45:40.004>
labels = ['3.9', 'docs']
title = 'What do "cased" and "uncased" mean?'
updated_at = <Date 2021-06-23.02:50:12.303>
user = 'https://bugs.python.org/otakutyrant'
bugs.python.org fields:
activity = <Date 2021-06-23.02:50:12.303>
actor = 'andrei.avk'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-05-19.03:45:40.004>
creator = 'otakutyrant'
dependencies = []
files = []
hgrepos = []
issue_num = 44175
keywords = ['patch']
message_count = 8.0
messages = ['393920', '393921', '393954', '393983', '393989', '394098', '394099', '396378']
nosy_count = 5.0
nosy_names = ['rhettinger', 'docs@python', 'josh.r', 'andrei.avk', 'otakutyrant']
pr_nums = ['26865']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue44175'
versions = ['Python 3.9']
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 reviewing PR #26865 and the migrated BPO issue 44175, including its discussion about the terms "cased" and "uncased." Locate the documentation change proposed there and confirm that the relevant definitions are clarified; the existing pull request shows that work is already underway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100