Martin v. Löwis added the comment: 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". ---------- priority: release blocker -> high _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15573> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
