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 ncoghlan
Recipients Arfrever, christian.heimes, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-11.19:03:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344711809.23.0.0129208724087.issue15573@psf.upfronthosting.co.za>
In-reply-to
Content
Short version:
3.3 implemented new constraints on memoryview equality comparisons to eliminate cases that were incorrectly returning True when they should have returned False.

However, the format constraints are currently too restrictive, so some memoryview comparisons that correctly returned True in 3.2 are now also returning False. This patch fixes *those* comparisons to once again return True.

Moving back to deferred blocked status, since the spurious false negatives are a regression from 3.2. It's fine for beta2 to ship with this problem, but it needs to be fixed for rc1.
History
Date User Action Args
2012-08-11 19:03:29ncoghlansetrecipients: + ncoghlan, loewis, georg.brandl, mark.dickinson, pitrou, vstinner, christian.heimes, Arfrever, skrah, meador.inge, python-dev
2012-08-11 19:03:29ncoghlansetmessageid: <1344711809.23.0.0129208724087.issue15573@psf.upfronthosting.co.za>
2012-08-11 19:03:28ncoghlanlinkissue15573 messages
2012-08-11 19:03:28ncoghlancreate