GNU bug report logs -
#37989
python2-numpy v1.17.3 fails to build
Previous Next
Reported by: Josh Holland <josh <at> inv.alid.pw>
Date: Wed, 30 Oct 2019 11:47:01 UTC
Severity: normal
Done: Marius Bakke <mbakke <at> fastmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hi,
It seems that the update of python-numpy to 1.17.3 in
8e5fbd5dda93e137ff527cabe25989b28ab9e1c0 has broken the build of the
corresponding Python 2 package, both on my local machine and on the CI
server: http://ci.guix.gnu.org/build/1893145/details.
The log in Cuirass is incomplete, but the error in my build is the
following:
starting phase `build'
running "python setup.py" with command "build" and parameters ()
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "setup.py", line 31, in <module>
raise RuntimeError("Python version >= 3.5 required.")
RuntimeError: Python version >= 3.5 required.
command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1
Indeed, despite the assertion on
https://numpy.org/doc/1.17/user/building.html that Python 2.7 or 3.4 are
sufficient, the setup.py script explicitly checks that Python is at
least 3.5; see the upstream commit badf2901:
https://github.com/numpy/numpy/commit/badf2901ea040aa89dbb3c19e53c6b1b692cb489
Lots of packages including libreoffice transitively depend on
python2-numpy, so this needs some sort of resolution — perhaps simply
pinning python2-numpy to a previous version? However, Python 2 will not
be maintained after the end of 2019, and I'm not sure if there is an
overall Guix-wide migration plan for python2-* packages.
--
Josh Holland
This bug report was last modified 5 years and 264 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.