Encoding issue in the name of the local DST timezone
Open
Nobody has claimed this yet.
OS-windows
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33259 |
|---|---|
| Nosy | @pganssle, @maggyero, @tirkarthi |
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 2018-04-10.21:34:20.688>
labels = ['type-bug', 'library']
title = 'Encoding issue in the name of the local DST timezone'
updated_at = <Date 2018-09-14.17:23:32.506>
user = 'https://github.com/maggyero'
bugs.python.org fields:
activity = <Date 2018-09-14.17:23:32.506>
actor = 'p-ganssle'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-04-10.21:34:20.688>
creator = 'maggyero'
dependencies = []
files = []
hgrepos = []
issue_num = 33259
keywords = []
message_count = 2.0
messages = ['315181', '325334']
nosy_count = 3.0
nosy_names = ['p-ganssle', 'maggyero', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33259'
versions = ['Python 3.6']
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 by locating the Python standard-library code for local DST timezone names and reproduce the encoding failure described by the title. The issue names no file, test, reproduction, or expected output, so clarify the intended encoding and acceptance criteria before adding a regression test or implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100