Inconsistent behavior with slice assignment?
Open
Nobody has claimed this yet.
docs
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32288 |
|---|---|
| Nosy | @stevendaprano, @bitdancer, @skrah, @serhiy-storchaka |
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-12-12.11:58:23.353>
labels = ['interpreter-core', 'type-bug', 'docs']
title = 'Inconsistent behavior with slice assignment?'
updated_at = <Date 2018-05-10.05:16:28.716>
user = 'https://bugs.python.org/MassimilianoCulpo'
bugs.python.org fields:
activity = <Date 2018-05-10.05:16:28.716>
actor = 'Massimiliano Culpo'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Interpreter Core']
creation = <Date 2017-12-12.11:58:23.353>
creator = 'Massimiliano Culpo'
dependencies = []
files = []
hgrepos = []
issue_num = 32288
keywords = []
message_count = 10.0
messages = ['308120', '308123', '308124', '308126', '308129', '308130', '308131', '308133', '316319', '316347']
nosy_count = 6.0
nosy_names = ['steven.daprano', 'r.david.murray', 'skrah', 'docs@python', 'serhiy.storchaka', 'Massimiliano Culpo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32288'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', '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
No source files, tests, reproduction, or entry points are named in the issue. Start by reading the linked BPO issue 32288 and its discussion to establish the expected slice-assignment behavior; the work is done only when that behavior is agreed and the relevant implementation or documentation has a corresponding regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100