PySequenceMethods documentation missing sq_slice and sq_ass_slice

Open
#70,534 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
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, python
Domain
api, documentation

Research direction

Start at the PySequenceMethods C API documentation and compare its documented members with the issue's missing sq_slice and sq_ass_slice entries. Done means both members are accurately documented in the relevant reference material; no file or test is named in the issue.

Written by the indexing model from the issue text.

Description

3.11 docs topic-C-API type-feature
BPO 26346
Nosy @vadmium

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-02-12.02:12:33.591>
labels = ['expert-C-API', '3.11', 'type-feature', 'docs']
title = 'PySequenceMethods documentation missing sq_slice and sq_ass_slice'
updated_at = <Date 2021-11-27.14:28:50.473>
user = 'https://bugs.python.org/atuining'

bugs.python.org fields:

activity = <Date 2021-11-27.14:28:50.473>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'C API']
creation = <Date 2016-02-12.02:12:33.591>
creator = 'atuining'
dependencies = []
files = []
hgrepos = []
issue_num = 26346
keywords = []
message_count = 3.0
messages = ['260154', '260160', '260161']
nosy_count = 3.0
nosy_names = ['atuining', 'docs@python', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue26346'
versions = ['Python 3.11']

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.