Supporting `strides` in `memoryview.cast`

Open
#85,398 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start by investigating the existing memoryview.cast behavior and the linked BPO issue 41226; the payload names no source files or tests. Define the expected behavior for accepting strides, then add coverage showing that memoryview.cast supports the intended stride cases.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) pending stdlib type-feature
BPO 41226
Nosy @vedgar, @jakirkham

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 2020-07-07.02:01:27.687>
labels = ['type-feature', 'library', '3.9', '3.10', '3.11']
title = 'Supporting `strides` in `memoryview.cast`'
updated_at = <Date 2022-01-13.19:54:52.107>
user = 'https://github.com/jakirkham'

bugs.python.org fields:

activity = <Date 2022-01-13.19:54:52.107>
actor = 'jakirkham'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-07-07.02:01:27.687>
creator = 'jakirkham'
dependencies = []
files = []
hgrepos = []
issue_num = 41226
keywords = []
message_count = 3.0
messages = ['373202', '402944', '410515']
nosy_count = 2.0
nosy_names = ['veky', 'jakirkham']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41226'
versions = ['Python 3.9', 'Python 3.10', '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.