On 30. 04. 23 17:00, Ben Beasley wrote:
sed -r -i 's/(numpy)==/\1>=/' pyproject.toml
Just in case you don't already know this.
If the listed dependency is numpy==1.23.2, the sed above works fine.
But if the the dependency was numpy==1.23.*, the sed would generate an invalid
requirement
On 30-04-2023 17:00, Ben Beasley wrote:
You’re right that project.dependencies has numpy>=1.22.3[1], but
upstream is also pinning numpy versions in the build-system.requires
section[2] in the same manner as oldest-supported-numpy[3]. This is for
PyPI distribution purposes; we don’t need to build
You’re right that project.dependencies has numpy>=1.22.3[1], but
upstream is also pinning numpy versions in the build-system.requires
section[2] in the same manner as oldest-supported-numpy[3]. This is for
PyPI distribution purposes; we don’t need to build wheels that support
numpy versions old
Hi,
I'm trying to build/update a package using mesonpy [1].
While going through the build process, exploring how the existing macros
behave together with mesonpy, I came across a weird build error, for
which I have not yet found a cause or explanation.
The build fails with [2]:
No matching
