Mutable Sequence Type works different for lists and bytearrays in slice[i:j:k]

Open
#56,815 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the linked slice_del.diff patches, including the version with the documentation change and the simplified test. Compare the existing slice[i:j:k] behavior for lists and bytearrays, then determine the intended consistent behavior from the patch discussion and documentation; done means the behavior, test coverage, and documentation agree.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 12606
Nosy @Yhg1s, @terryjreedy, @ezio-melotti, @py-user, @serhiy-storchaka
Files
  • slice_del.diff: Patch
  • slice_del.diff: patch including doc change
  • slice_del.diff
  • slice_del.diff: simplified test
  • slice_del.diff: version without double type cast
    		•

    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 2011-07-21.22:31:34.463>
labels = ['interpreter-core', 'type-feature']
title = 'Mutable Sequence Type works different for lists and bytearrays in slice[i:j:k]'
updated_at = <Date 2016-01-03.09:27:27.677>
user = 'https://github.com/py-user'

    bugs.python.org fields:

    activity = <Date 2016-01-03.09:27:27.677>
actor = 'py.user'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-07-21.22:31:34.463>
creator = 'py.user'
dependencies = []
files = ['38912', '38913', '38930', '38932', '38941']
hgrepos = []
issue_num = 12606
keywords = ['patch']
message_count = 9.0
messages = ['140832', '140835', '140845', '140846', '240586', '240635', '241605', '257341', '257407']
nosy_count = 6.0
nosy_names = ['twouters', 'terry.reedy', 'ezio.melotti', 'py.user', 'serhiy.storchaka', 'siegfried.gevatter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue12606'
versions = ['Python 3.5', 'Python 3.6']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.