errors raised by bytes() and bytearray() for invalid size argument
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29841 |
|---|---|
| Nosy | @vstinner, @serhiy-storchaka, @orenmn |
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 2017-03-17.20:33:15.921>
labels = ['interpreter-core', 'type-feature', '3.7']
title = 'errors raised by bytes() and bytearray() for invalid size argument'
updated_at = <Date 2017-03-24.20:47:05.648>
user = 'https://github.com/orenmn'
bugs.python.org fields:
activity = <Date 2017-03-24.20:47:05.648>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2017-03-17.20:33:15.921>
creator = 'Oren Milman'
dependencies = []
files = []
hgrepos = []
issue_num = 29841
keywords = []
message_count = 2.0
messages = ['289783', '289785']
nosy_count = 3.0
nosy_names = ['vstinner', 'serhiy.storchaka', 'Oren Milman']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue29841'
versions = ['Python 3.7']
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
The issue names no files, tests, or entry points. Start by locating the interpreter handling for bytes() and bytearray() with invalid size arguments, then review the migrated bug report details. Done means implementing the requested error behavior and adding tests, but the exact expected errors are not specified here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100