-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best practice for pinning min version in anaconda-project.yml #275
Comments
It's great to have this info when a notebook is first contributed to this repo. And if we had a feature in conda to "install like it's April 2021" or similar (which I think I requested years ago), it would be great to have this info recorded retroactively for the existing notebooks. It's a bit confusing when it's a notebook from 2016 with a solve done in 2023, since those are not the minimum versions this notebook should work with. So I'm not sure whether it's helpful or confusing to add this info for existing older notebooks. |
Having the information on the minimum set of pins would be useful in many ways I'm sure but:
|
Yep - makes sense and agree that it is cumbersome to do this. |
Sorry - accidentally closed it. But I think this is resolved as above and can be closed. |
Benefit
Adding a lower bound on package versions in the anaconda-project.yml makes it easy to see min requirement at the time of lock file generation without actually looking at the lock file. This is convenient and nice for sure.
Cost
We already have a lock file with this info even if it's not convenient for a human to read/parse.
Is this nice to have for all packages in anaconda-project.yml? If so, should we consider writing a script to automatically get the min versions for packages that are unpinned from reading the lock file? I did this in a quick way and while the min versions look correct, I'm not sure the solver will resolve to the same lock file.
Curious to know if:
Thanks!
The text was updated successfully, but these errors were encountered: