Matthew R. Becker
Matthew R. Becker
This is a conda-build error, not a linter error. It appears you need to rerender the feedstock.
I made a few PRs to help with this. Comments welcome!
For grayskull updates, I think it simply injects the minimum by hand anyways, so this is a non-issue?
Also note that the hint literally says "or change the build configuration as needed to match the constraints of their specific package."
Ah I see what you mean. Does the jinja2 override actually work? We have python_min in the global pinnings too and I am unsure which item takes precedence when jinja2...
My general feeling is that carrying important state in jinja2 is not a best practice, but I do see the advantage of not having conda_build_config,yaml files around for `noarch: python`...
ok I am happy to change the docs and linter to suggest context and/or jinja2. We need to ensure that rattler and conda-build have the same precedence order with respect...
I tested rattler-build overrides and they work fine. I did however find an odd feature where rattler build treats recipe pins like ```yaml requirements: run: - python 3.10 ``` as...
Ah darn. I know what the bug is. Will fix it.
https://github.com/conda-forge/conda-smithy/pull/2132