validate mime types loaded from system files. Document that system files take precedence.
Open
Nobody has claimed this yet.
3.11
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32462 |
|---|---|
| Nosy | @bitdancer, @csabella, @iritkatriel |
| 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 2017-12-31.11:07:49.291>
labels = ['type-feature', 'library', '3.11']
title = 'validate mime types loaded from system files. Document that system files take precedence.'
updated_at = <Date 2022-01-18.13:39:10.730>
user = 'https://github.com/csabella'
bugs.python.org fields:
activity = <Date 2022-01-18.13:39:10.730>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-12-31.11:07:49.291>
creator = 'cheryl.sabella'
dependencies = []
files = []
hgrepos = []
issue_num = 32462
keywords = ['patch']
message_count = 4.0
messages = ['309275', '309291', '410864', '410865']
nosy_count = 3.0
nosy_names = ['r.david.murray', 'cheryl.sabella', 'iritkatriel']
pr_nums = ['5063']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32462'
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 with the Library (Lib) component and review the existing python/cpython#5063 patch, since no files or tests are named in the issue. Confirm the mime types loaded from system files are validated, document that those files take precedence, and verify the relevant tests cover both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100