extended slicing not sufficiently covered in docs

Open
#51,709 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the migrated BPO issue 7460 and the existing Python documentation coverage for extended slicing. Identify the specific gaps described there, update the relevant documentation, and verify that the missing slicing behavior is clearly covered.

Written by the indexing model from the issue text.

Description

docs type-feature
BPO 7460
Nosy @birkenfeld, @terryjreedy

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 2009-12-08.17:20:56.139>
labels = ['type-feature', '3.8', '3.9', '3.10', 'docs']
title = 'extended slicing not sufficiently covered in docs'
updated_at = <Date 2020-11-21.16:51:08.801>
user = 'https://bugs.python.org/donlorenzo'

bugs.python.org fields:

activity = <Date 2020-11-21.16:51:08.801>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2009-12-08.17:20:56.139>
creator = 'donlorenzo'
dependencies = []
files = []
hgrepos = []
issue_num = 7460
keywords = []
message_count = 3.0
messages = ['96141', '100501', '100503']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'terry.reedy', 'donlorenzo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue7460'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

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.