➜

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 loewis
Recipients Arfrever, christian.heimes, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-10.06:29:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344580190.66.0.854066587643.issue15573@psf.upfronthosting.co.za>
In-reply-to
Content 
haypo: thanks for stating the issue.

ISTM that this classifies as an "obscure" bug: you have to use memoryviews, and you need to compare them for equality, and the comparison needs to be "non-trivial", where "trivial" is defined 
by "both are 1D byte arrays".

While this is a bug, I think it still can be fixed in a bug fix 
release of 3.3, so un-blocking.

I also think that as a first step, a specification needs to be
drafted defining when exactly a memory view should compare equal
with some other object. I can easily provide a specification that
makes the current implementation "correct".
History
Date User Action Args
2012-08-10 06:29:51loewissetrecipients: + loewis, georg.brandl, mark.dickinson, ncoghlan, pitrou, vstinner, christian.heimes, Arfrever, skrah, meador.inge, python-dev
2012-08-10 06:29:50loewissetmessageid: <1344580190.66.0.854066587643.issue15573@psf.upfronthosting.co.za>
2012-08-10 06:29:50loewislinkissue15573 messages
2012-08-10 06:29:49loewiscreate