Closed jfolz closed 1 year ago
This is the end of the build output: https://paste.debian.net/1199603/
We provision the builders with apt's numpy (1.16.2 in Buster) and also let pip upgrade it. I'm not sure how build requirements work with pre-installed packages?
At the top we can see numpy==1.14.5
being installed, which is correct. My understanding is that pip is supposed to provide an isolated build environment (through pep517
, in this case vendored into pip). That is the default when a PEP 517-compatible distribution is detected and has to be turned off with --no-build-isolation
. The isolation is clearly not working here as the build is referencing files in /usr/local/lib/python3.7/dist-packages/numpy
instead of some temp directory.
I don't see the issue in recent builds. Closing.
Package name: simplejpeg Link to PyPI page: https://pypi.org/project/simplejpeg/ Link to piwheels page: https://www.piwheels.org/project/simplejpeg/ Version: 1.6.1 Python version: at least 3.7, but probably all I am the maintainer: Yes More information:
With 1.6.1 simplejpeg conforms to PEP517 and is specified to build against
oldest-supported-numpy
. Here's thepyproject.toml
:oldest-supported-numpy
is a meta package that requires the oldest version of numpy that works with the current Python version:From the looks of things the shown versions are available from piwheels.
piwheels seems to not respect this requirement:
This results in
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 44 from C header, got 40 from PyObject
.As you can see it only works with 1.20.0 since the size of ndarray changed, so I believe piwheels built against
numpy>=1.20
instead ofoldest-supported-numpy
.