[issue30623] python-nightly import numpy fails since recently

Changes by Ned Deily : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue30623] python-nightly import numpy fails since recently

Thomas Caswell added the comment: https://github.com/python/cpython/pull/1236 has been merged, I believe this issue can be closed. -- nosy: +tcaswell ___ Python tracker

[issue30623] python-nightly import numpy fails since recently

R. David Murray added the comment: There is a possible future in which the development style is based around continuous integration with third parties, where we apply our backward compatibility policy even to changes from one commit to the next within our development cycle. I think that

[issue30623] python-nightly import numpy fails since recently

Arek Bulski added the comment: Thank you, I will temporarily remove the numpy unit test from the 3.7 until I get notification that it was fixed. sob., 10 cze 2017 o 22:48 użytkownik STINNER Victor napisał: > > Changes by STINNER Victor : > > >

[issue30623] python-nightly import numpy fails since recently

Changes by STINNER Victor : -- pull_requests: +2151 ___ Python tracker ___ ___

[issue30623] python-nightly import numpy fails since recently

Nathaniel Smith added the comment: @Arek: It's great that you're testing your code against the latest 3.7 pre-release, because that helps give early warning of issues in CPython as its developed, which helps everyone. BUT, you really cannot expect to use in-development versions and expect

[issue30623] python-nightly import numpy fails since recently

Arek Bulski added the comment: Oh good point, but when I submitted this on TravisCI issues they pointed me to here. And this is a highest priority bug. sob., 10 cze 2017 o 21:02 użytkownik Jelle Zijlstra napisał: > > Jelle Zijlstra added the comment: > > Sounds like

[issue30623] python-nightly import numpy fails since recently

Jelle Zijlstra added the comment: Sounds like the issue is with numpy, not CPython, so there's little reason to keep this CPython bug open. -- ___ Python tracker

[issue30623] python-nightly import numpy fails since recently

Arek Bulski added the comment: Negative, this bug causes TravisCI to fail on every commit regardless of code. Please treat this tickes as highest priority. sob., 10 cze 2017 o 20:54 użytkownik Ned Deily napisał: > > Ned Deily added the comment: > > Can we close this

[issue30623] python-nightly import numpy fails since recently

Ned Deily added the comment: Can we close this issue then? -- nosy: +ned.deily ___ Python tracker ___ ___

[issue30623] python-nightly import numpy fails since recently

Nathaniel Smith added the comment: It's because Julian thinks _PyTraceMalloc_Untrack is going to lose its underscore in 3.7, so he made numpy assume that. Numpy issue, I'll see what we can do. -- ___ Python tracker

[issue30623] python-nightly import numpy fails since recently

Jelle Zijlstra added the comment: The error is /home/travis/virtualenv/python3.7-dev/lib/python3.7/site-packages/numpy/core/multiarray.cpython-37m-x86_64-linux-gnu.so: undefined symbol: PyTraceMalloc_Untrack. On a quick look I couldn't find any recent changes in CPython related to

[issue30623] python-nightly import numpy fails since recently

Changes by Antoine Pitrou : -- nosy: +njs ___ Python tracker ___ ___ Python-bugs-list mailing

[issue30623] python-nightly import numpy fails since recently

New submission from Arek Bulski: About few days ago python-nightly started failing on TravisCI for no reason, and I dont think its due to my code. In fact it fails on importing numpy but fails to get into catch ImportError. This is a recent BUG. Build log: