calendar should understand full- vs. half-width characters
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- internationalization
Research direction
Start by reading Python's calendar module and the referenced dependency, bpo-12568, which concerns character width in columns. Determine the expected handling of full- and half-width characters and identify the relevant tests or entry points; done means the behavior is specified and covered by tests.
Written by the indexing model from the issue text.
Description
| BPO | 17048 |
|---|---|
| Nosy | @rhettinger, @terryjreedy, @ezio-melotti, @chason, @ishigoya |
| Dependencies |
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 2013-01-27.08:38:10.091>
labels = ['type-feature', 'library']
title = 'calendar should understand full- vs. half-width characters'
updated_at = <Date 2018-01-29.05:13:25.560>
user = 'https://bugs.python.org/nneonneo'
bugs.python.org fields:
activity = <Date 2018-01-29.05:13:25.560>
actor = 'chason.chaffin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-01-27.08:38:10.091>
creator = 'nneonneo'
dependencies = ['12568']
files = []
hgrepos = []
issue_num = 17048
keywords = []
message_count = 4.0
messages = ['180748', '180751', '181154', '311001']
nosy_count = 6.0
nosy_names = ['rhettinger', 'terry.reedy', 'nneonneo', 'ezio.melotti', 'chason.chaffin', 'ishigoya']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17048'
versions = ['Python 3.4']
- 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