Improve error messages for Windows reserved file names
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
No source files or tests are named in the issue. Start by reviewing the original issue 37517 and locating Python's Windows reserved-file-name error handling; done means the requested error-message improvements are implemented and covered by relevant tests.
Written by the indexing model from the issue text.
Description
| BPO | 37517 |
|---|---|
| Nosy | @pfmoore, @tjguk, @stevendaprano, @zware, @eryksun, @zooba, @https://github.com/cknoll/ |
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 2019-07-07.00:00:34.838>
labels = ['type-feature', '3.8', 'OS-windows']
title = 'Improve error messages for Windows reserved file names'
updated_at = <Date 2019-07-10.08:38:13.659>
user = 'https://github.com/stevendaprano'
bugs.python.org fields:
activity = <Date 2019-07-10.08:38:13.659>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-07-07.00:00:34.838>
creator = 'steven.daprano'
dependencies = []
files = []
hgrepos = []
issue_num = 37517
keywords = ['3.6regression']
message_count = 4.0
messages = ['347456', '347465', '347537', '347610']
nosy_count = 8.0
nosy_names = ['paul.moore', 'tim.golden', 'steven.daprano', 'SilentGhost', 'zach.ware', 'eryksun', 'steve.dower', 'CarK']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37517'
versions = ['Python 3.8']
- 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