Some code comments refer to removed initfsencoding()
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Search the repository for references to initfsencoding() and inspect the surrounding comments. Update comments that describe the removed function, then verify that no outdated comment references remain.
Written by the indexing model from the issue text.
Description
| BPO | 41012 |
|---|---|
| Nosy | @manueljacob |
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-06-17.22:39:43.196>
labels = []
title = 'Some code comments refer to removed initfsencoding()'
updated_at = <Date 2020-06-17.22:39:43.196>
user = 'https://github.com/manueljacob'
bugs.python.org fields:
activity = <Date 2020-06-17.22:39:43.196>
actor = 'mjacob'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-06-17.22:39:43.196>
creator = 'mjacob'
dependencies = []
files = []
hgrepos = []
issue_num = 41012
keywords = []
message_count = 1.0
messages = ['371779']
nosy_count = 1.0
nosy_names = ['mjacob']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue41012'
versions = []
- 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 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·