➜

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 Thomas.Robitaille, brett.cannon, martin.panter, mdk, ncoghlan, ned.deily, python-dev, serhiy.storchaka, vstinner
Date 2016-12-09.03:20:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481253611.29.0.743068004504.issue28835@psf.upfronthosting.co.za>
In-reply-to
Content 
If the intended reference was to #28897, then yes, it was related: NumPy had introduced a workaround for the regression that existed in the beta releases (presumably thinking it was an intentional change that just hadn't been added to the porting guide yet), and this fix for the regression broke their workaround.

Reverting the workaround on the NumPy side restored compatibility :)
History
Date User Action Args
2016-12-09 03:20:11ncoghlansetrecipients: + ncoghlan, brett.cannon, vstinner, ned.deily, python-dev, martin.panter, serhiy.storchaka, Thomas.Robitaille, mdk
2016-12-09 03:20:11ncoghlansetmessageid: <1481253611.29.0.743068004504.issue28835@psf.upfronthosting.co.za>
2016-12-09 03:20:11ncoghlanlinkissue28835 messages
2016-12-09 03:20:10ncoghlancreate