This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients belopolsky, seberg, skrah
Date 2014-10-02.14:24:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412259864.08.0.604570083279.issue22445@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, I think it would be good to make this change early in the
3.5 release cycle, so issues can be found.  Sebastian, do you
have an idea when the change will be decided in numpy?


Regarding the discussion here ...

   https://github.com/numpy/numpy/issues/5085

... about the special stride marker:


In the case of slicing it would be nice to use the "organic" value
that would arise normally from computing the slice. That helps in checking other PEP-3118 implementations like Modules/_testbuffer.c
against numpy.
History
Date User Action Args
2014-10-02 14:24:24skrahsetrecipients: + skrah, belopolsky, seberg
2014-10-02 14:24:24skrahsetmessageid: <1412259864.08.0.604570083279.issue22445@psf.upfronthosting.co.za>
2014-10-02 14:24:24skrahlinkissue22445 messages
2014-10-02 14:24:23skrahcreate