-
Notifications
You must be signed in to change notification settings - Fork 5
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
Switch to using Conda lock files to specify requirements and update dependencies #949
Conversation
Currently CI not running correctly, I think probably because of EDIT: I think I was misreading the log previously - looks like the problem is only with |
Conda has been installed on the runners. |
Also need to install tox-conda...doing that now |
Interesting, when I ran locally I didn't need to install |
Moving to conda requires sorting the tox config, GHA self-hosted runners, the container used by Azure Batch. It might not be straightforward. So, I have a suggestion: let's hold off installing the packages from conda i.e. simply update the files in requirements to update the dependencies. We can then start benefitting from all the work you've put in to this quickly. Then look at all these moving parts together and rationalise our approach. @giordano will be also be able to contribute to this. |
I don't think we want to go forward with this one any more so closing. |
Switches from using
pip-compile
andrequirements.txt
files to specify Python dependencies to be installed usingpip
to usingconda-lock
to generate lock files specifying (platform specific) Conda environments with both Python and non-Python dependencies.Also currently set to update dependencies to Python 3.11 and Pandas 2.0.0 - we could potentially pin to the current Python (v3.8) / Pandas (v1.2.2) versions instead to split the change over how we're handling dependencies and the actual updating of dependencies.