Hello,
Is there any reason to have an upper bound restriction on maturin in pyproject.toml ?
We're building and testing tlparse for riscv64 as part of a larger project where we’re trying to build and deploy the most common Python binary packages for riscv64. See https://gitlab.com/riseproject/python/wheel_builder for more info).
To build riscv64 wheels, we need at least maturin 1.7.1. Right now, we’re using maturin 1.8.1, and tlparse 0.3.39 is building and testing fine (see https://gitlab.com/riseproject/python/tlparse/-/jobs/9682558261). The only catch is that we’ve had to patch the pyproject.toml and keep that patch across versions. We usually try to avoid patching stuff to keep maintenance simple, so I was wondering if there’s any way around this restriction.
Hello,
Is there any reason to have an upper bound restriction on maturin in
pyproject.toml?We're building and testing tlparse for riscv64 as part of a larger project where we’re trying to build and deploy the most common Python binary packages for riscv64. See https://gitlab.com/riseproject/python/wheel_builder for more info).
To build riscv64 wheels, we need at least
maturin 1.7.1.Right now, we’re usingmaturin 1.8.1, andtlparse 0.3.39is building and testing fine (see https://gitlab.com/riseproject/python/tlparse/-/jobs/9682558261). The only catch is that we’ve had to patch thepyproject.tomland keep that patch across versions. We usually try to avoid patching stuff to keep maintenance simple, so I was wondering if there’s any way around this restriction.