Closed theavey closed 1 hour ago
Hi @theavey - that is a featuer called "run-exports". Python (from conda-forge) automatically adds a run-dependency on this particular package to make sure that it will only be run with this particular version of python.
If you determine that you don't need that you can disable the specific run exports by using the ignore_run_exports
field: https://prefix-dev.github.io/rattler-build/latest/reference/recipe_file/#ignore-run-exports
For example, you could say:
requirements:
ignore_run_exports:
by_name:
- python_abi
Okay, so just user error in this case :)
Thank you for the info!
I am building a package for Windows-only on Windows. It uses a wheel to install and runs a simple script to copy over some files. The wheel is compatible with Python 3.7 through 3.12, so I added that requirement in the run section. As I understand it, the
host
Python requirement has no version restriction, so I did not restrict that.However, when I run the build, the host environment uses Python 3.13, and for some reason, this adds a requirement of
python_abi 3.13.*
to the built package, which is not actually required and then breaks when trying to build the test environment (because it requires Python <3.13 but also python_abi 3.13.*, which are obviously incompatible.Kinda seems related to #344, but I cannot say for sure if they are the same.
Here is the
recipe.yaml
Using rattler-build 0.30.0