homepage

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:52:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344714768.57.0.382120950154.issue15573@psf.upfronthosting.co.za>
In-reply-to
Content
Hmm, you're right. OK, here's a simpler proposal for 3.3:
1. Always look at shape first. If they're different, then they're not equal
2. If both formats are known, compare by unpacked value
3. If either format is unknown, compare by memory contents (just like 3.2)
The fallback case should then behave exactly like 3.2 (since 3.2 really couldn't handle anything other than 1D data and always ignored the format info).
I'd be happier if the compare-by-value didn't make complete copies of the entire array though.
History
Date User Action Args
2012年08月11日 19:52:48ncoghlansetrecipients: + ncoghlan, loewis, georg.brandl, mark.dickinson, pitrou, vstinner, christian.heimes, Arfrever, skrah, meador.inge, python-dev
2012年08月11日 19:52:48ncoghlansetmessageid: <1344714768.57.0.382120950154.issue15573@psf.upfronthosting.co.za>
2012年08月11日 19:52:48ncoghlanlinkissue15573 messages
2012年08月11日 19:52:47ncoghlancreate

AltStyle によって変換されたページ (->オリジナル) /