ci-conda: change spelling of python dependency#214
ci-conda: change spelling of python dependency#214jameslamb merged 2 commits intorapidsai:mainfrom jameslamb:fix/spec
Conversation
|
It looks to me like this is working! For example, in a successful |
bdice
left a comment
There was a problem hiding this comment.
Thanks for the fix. For awareness, in the past we just used pinnings like python=3.10. See here for historical context: https://github.com/rapidsai/miniforge-cuda/pull/52/files
That would definitely be simpler, and as far as I know should still achieve what we want.. @jakirkham what was the reason for switching from Looks like that was also carried over to this repo #167, but I don't see any discussion about it there. (cc @hcho3 in case you remember) I'll merge this right now to unblock CI, but would be happy to come back and switch this to |
|
Also in #207 I had to add some logic to use a different build tag. It would be easy to compute the upper bound there rather than supplying it as an input. We can discuss on that PR. |
Proposes changing the spelling of the Python dependency for conda builds here from something like this:
to something like this:
To work around an issue with parsing
~=in recent versions ofmamba.References:
MatchSpecparsing error with~=version operator mamba-org/mamba#3647