Improvement mktime error reporting
Open
Nobody has claimed this yet.
extension-modules
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44413 |
|---|---|
| Nosy | @malemburg, @terryjreedy, @abalkin, @tiran, @pganssle, @corona10, @Fidget-Spinner, @akulakov, @wasade |
| 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 2021-06-13.18:02:13.156>
labels = ['type-bug', '3.9', '3.10', '3.11']
title = 'Improvement mktime error reporting'
updated_at = <Date 2021-12-20.22:45:30.454>
user = 'https://bugs.python.org/psijic'
bugs.python.org fields:
activity = <Date 2021-12-20.22:45:30.454>
actor = 'wasade'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-06-13.18:02:13.156>
creator = 'psijic'
dependencies = []
files = []
hgrepos = []
issue_num = 44413
keywords = []
message_count = 15.0
messages = ['395758', '396102', '397600', '407346', '408615', '408627', '408642', '408644', '408650', '408658', '408659', '408660', '408977', '408978', '408979']
nosy_count = 10.0
nosy_names = ['lemburg', 'terry.reedy', 'belopolsky', 'christian.heimes', 'p-ganssle', 'corona10', 'kj', 'andrei.avk', 'psijic', 'wasade']
pr_nums = ['30124']
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44413'
versions = ['Python 3.9', 'Python 3.10', '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 by reading the linked pull request #30124 and the original BPO issue 44413. The issue text names no source file, test, or acceptance criteria, so use the proposed error-reporting behavior and discussion to identify the affected code and tests. The work is done when the agreed behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100