python / python/cpython

Slice confusing with negative stop and strides and the 0th element.

Open
#73,068 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) docs
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 28882
Nosy @terryjreedy, @hardkrash, @vadmium, @MojoVampire

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 2016-12-06.05:06:40.291>
labels = ['3.7', 'docs']
title = 'Slice confusing with negative stop and strides and the 0th element.'
updated_at = <Date 2016-12-10.00:28:35.180>
user = 'https://github.com/hardkrash'

bugs.python.org fields:

activity = <Date 2016-12-10.00:28:35.180>
actor = 'martin.panter'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-12-06.05:06:40.291>
creator = 'hardkrash'
dependencies = []
files = []
hgrepos = []
issue_num = 28882
keywords = []
message_count = 6.0
messages = ['282500', '282501', '282578', '282801', '282810', '282814']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'hardkrash', 'docs@python', 'martin.panter', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue28882'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7']

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.

Research direction

Start by reading the discussion in BPO issue 28882 and the Python slicing documentation, focusing on negative stops, strides, and index 0. The work is done when the documentation clearly explains the reported slicing cases and the issue's confusion is resolved without changing Python behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.