Misleading information about slice assignment in docs

Open
#62,139 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing BPO issue 17939 and the Python documentation related to slice assignment; the issue does not name a documentation file or test. Identify the misleading wording and update it so the slice-assignment behavior is accurately explained, then verify the documentation change renders correctly.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) docs type-feature
BPO 17939
Nosy @terryjreedy, @ezio-melotti

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 2013-05-08.21:31:39.955>
labels = ['type-feature', '3.8', '3.9', '3.10', 'docs']
title = 'Misleading information about slice assignment in docs'
updated_at = <Date 2020-11-17.15:23:56.125>
user = 'https://bugs.python.org/stefanchrobot'

bugs.python.org fields:

activity = <Date 2020-11-17.15:23:56.125>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2013-05-08.21:31:39.955>
creator = 'stefanchrobot'
dependencies = []
files = []
hgrepos = []
issue_num = 17939
keywords = []
message_count = 2.0
messages = ['188738', '188870']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'ezio.melotti', 'docs@python', 'stefanchrobot']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17939'
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.