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 charris44
Recipients charris44, mdk, ned.deily, pitrou, serhiy.storchaka, vstinner
Date 2016-12-07.23:03:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481151789.4.0.00892977054655.issue28897@psf.upfronthosting.co.za>
In-reply-to
Content
I ran with Python 3.6.0rc1 (default, Dec  7 2016, 14:00:51) and get the same errors in both NumPy 1.13.0-dev and 1.12. But I gave you a wrong suggestion, we disable some test errors for releases, which is what is on PyPI, and that is doubtless why you don't see them. My fault, and I apologize. You will probably need to clone the github repo (https://github.com/numpy/numpy) and do a `python3.6 runtests.py` in the master branch to see the problem. 

I'm suspecting the problem needs to be fixed on the numpy end, but need to know what the changes were made to get an idea of a fix. We do some odd stuff with the warnings queue in order to make sure no warnings are inadvertently disabled in the tests.
History
Date User Action Args
2016-12-07 23:03:09charris44setrecipients: + charris44, pitrou, vstinner, ned.deily, serhiy.storchaka, mdk
2016-12-07 23:03:09charris44setmessageid: <1481151789.4.0.00892977054655.issue28897@psf.upfronthosting.co.za>
2016-12-07 23:03:09charris44linkissue28897 messages
2016-12-07 23:03:09charris44create