struct.pack error messages do not indicate which argument was invalid
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with the struct.pack implementation and inspect the existing linked PRs gh-103657 and gh-132857. Check how invalid arguments are currently reported and whether the relevant tests cover these errors. Done means struct.pack error messages identify which argument was invalid.
Written by the indexing model from the issue text.
Description
| BPO | 23578 |
|---|---|
| Nosy | @mdickinson, @meadori, @serhiy-storchaka, @mlouielu |
| 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 = 'https://github.com/serhiy-storchaka'
closed_at = None
created_at = <Date 2015-03-03.17:03:05.610>
labels = ['easy', 'type-feature', 'library', '3.11']
title = 'struct.pack error messages do not indicate which argument was invalid'
updated_at = <Date 2022-03-24.00:24:53.123>
user = 'https://bugs.python.org/alynn'
bugs.python.org fields:
activity = <Date 2022-03-24.00:24:53.123>
actor = 'iritkatriel'
assignee = 'serhiy.storchaka'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-03-03.17:03:05.610>
creator = 'alynn'
dependencies = []
files = []
hgrepos = []
issue_num = 23578
keywords = ['easy (C)']
message_count = 4.0
messages = ['237153', '288565', '288569', '288570']
nosy_count = 5.0
nosy_names = ['mark.dickinson', 'meador.inge', 'serhiy.storchaka', 'alynn', 'louielu']
pr_nums = ['291']
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23578'
versions = ['Python 3.11']
Linked PRs
- gh-103657
- gh-132857
- 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 ·