[issue4580] slicing of memoryviews when itemsize != 1 is wrong

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

>   * I don't see where array.array getbuf implementation is broken.  It
> looks correct to me.  It sets view.shape to NULL unless the consumer
> asked for the shape information to be reported in which case it sets it
> equal to a pointer to the number of elements in the array.

What I meant by that is that array.array frequently bypasses its own
resize helper and calls PyMem_Resize directly instead. This is the
likely cause of #4583.

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4580>
_______________________________________