external strftime for Python?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Review the linked BPO issue and uploaded strftime.diff first; the issue provides no current repository files or tests. Determine the intended external strftime behavior and identify the affected Python tests before defining what completion should mean.
Written by the indexing model from the issue text.
Description
| BPO | 3173 |
|---|---|
| Nosy | @gvanrossum, @loewis, @amauryfa, @abalkin, @vstinner, @ericvsmith, @merwok, @florentx, @berkerpeksag |
| Files |
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 2008-06-23.02:44:52.698>
labels = ['type-feature']
title = 'external strftime for Python?'
updated_at = <Date 2014-06-29.22:36:42.704>
user = 'https://github.com/smontanaro'
bugs.python.org fields:
activity = <Date 2014-06-29.22:36:42.704>
actor = 'belopolsky'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2008-06-23.02:44:52.698>
creator = 'skip.montanaro'
dependencies = []
files = ['10704']
hgrepos = []
issue_num = 3173
keywords = ['patch']
message_count = 17.0
messages = ['68603', '68604', '68606', '69092', '75730', '107168', '107315', '111886', '111954', '125579', '125584', '125585', '125587', '125588', '125589', '146853', '163132']
nosy_count = 11.0
nosy_names = ['gvanrossum', 'loewis', 'amaury.forgeotdarc', 'belopolsky', 'vstinner', 'eric.smith', 'schmir', 'eric.araujo', 'cvrebert', 'flox', 'berker.peksag']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue3173'
versions = ['Python 3.3']
- 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 ·