Matthew R. Becker
Matthew R. Becker
Yeah that'd be fine too.
Yeah the key is to parameterize the bound so the ecosystem moves and we eliminate crazy solves. We do lint on this already, but we don't lint on moving the...
Note that we don't actually need to pin the bound in host if we parameterize it globally. We could use `>= {{ min_python_ver }}` in all sections and it'd be...
Yeah people can add a bound instead of overriding (say `minpy=3.9`): ``` host: - python >={{ minpy }} - python >=3.11 run: - python >={{ minpy }} - python >=3.11...
Yeah I am happy with an `==` in host. My main thing is that we should have a global pinning value for it. From my perspective, `noarch` packages fail on...
So I think our consensus is to have ```yaml host: - python {{ minpy }} run: - python >={{ minpy }} test: requires: - python ={{ minpy }} ``` We'll...
It is unclear to me if @dopplershift's comment is for - not supporting 3.9 for noarch when we still support it as part of our standard build matrix or if...
@ocefpaf If we parameterize the bound in the pinnings, it should be easy enough to roll back globally via a custom pinnings file for your delay, right? > So then...
We ship conda packages. Mixing pip and conda is asking for trouble.
OK so I think we're at consensus. We'll do the usual, announcement + migrator + lint + hint thing here.