PEP-3118: C-contiguity with zero strides

[skrah]

BPO	12845
Nosy	@skrah

^{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 = 'https://github.com/skrah'
closed_at = <Date 2014-09-19.21:12:38.457>
created_at = <Date 2011-08-26.10:29:44.632>
labels = ['interpreter-core', 'type-bug', 'invalid']
title = 'PEP-3118: C-contiguity with zero strides'
updated_at = <Date 2014-09-19.21:12:38.454>
user = 'https://github.com/skrah'

bugs.python.org fields:

activity = <Date 2014-09-19.21:12:38.454>
actor = 'skrah'
assignee = 'skrah'
closed = True
closed_date = <Date 2014-09-19.21:12:38.457>
closer = 'skrah'
components = ['Interpreter Core']
creation = <Date 2011-08-26.10:29:44.632>
creator = 'skrah'
dependencies = []
files = []
hgrepos = []
issue_num = 12845
keywords = []
message_count = 3.0
messages = ['143005', '221481', '227123']
nosy_count = 2.0
nosy_names = ['skrah', 'BreamoreBoy']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12845'
versions = ['Python 3.5']

[skrah]

Numpy and PyBuffer_IsContiguous() have different ideas of
C-contiguity if there is a zero in strides (this is allowed,
I asked Pauli Virtanen).

>>> from numpy import *
>>> nd = ndarray(shape=[10], strides=[0])
>>> nd.flags
  C_CONTIGUOUS : True
  F_CONTIGUOUS : False
  OWNDATA : True
  WRITEABLE : True
  ALIGNED : True
  UPDATEIFCOPY : False
>>> 
>>> from _testbuffer import ndarray as pyarray
>>> from _testbuffer import PyBUF_FULL_RO
>>> x = pyarray(nd, getbuf=PyBUF_FULL_RO)
>>> x.c_contiguous
False

[BreamoreBoy]

What is the status of this issue as according to the index PEP-3118 has been completed?

[skrah]

This was a bug in NumPy that has been fixed.