Comparison of memoryview

Open
#64,598 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the migrated issue details and the original bugs.python.org issue 20399; the payload names no source file or test. Clarify the intended comparison behavior for memoryview and locate the relevant interpreter-core entry points and tests before implementation. Done means the agreed behavior is covered by tests.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 20399
Nosy @pitrou, @MojoVampire, @remilapeyre, @ironage

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 2014-01-26.20:37:37.194>
labels = ['interpreter-core', 'type-feature', '3.8']
title = 'Comparison of memoryview'
updated_at = <Date 2019-04-02.19:16:07.171>
user = 'https://bugs.python.org/finswimmer'

bugs.python.org fields:

activity = <Date 2019-04-02.19:16:07.171>
actor = 'james stone'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-01-26.20:37:37.194>
creator = 'fin.swimmer'
dependencies = []
files = []
hgrepos = []
issue_num = 20399
keywords = []
message_count = 9.0
messages = ['209351', '209373', '209421', '209449', '333985', '333987', '334009', '334013', '339363']
nosy_count = 5.0
nosy_names = ['pitrou', 'fin.swimmer', 'josh.r', 'remi.lapeyre', 'james stone']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue20399'
versions = ['Python 3.8']

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.