-
Notifications
You must be signed in to change notification settings - Fork 1
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
13 clarifying environment setup in readme #16
base: dev
Are you sure you want to change the base?
Conversation
Adding steps for environment creation
Removed package releases, and specifying a more recent python version
updating python to 3.10
adding conda init in CI before conda activate
I'm looking into why the existing CIs are failing. |
fixing venv tests
fixing conda env activation during tests
fixing conda setup
reactivating the terminal
persist shell
fixing
minimal version
@crangelsmith after lots of attempts, I've finally gottent the conda CI pipeline to work as well, but had to use a strange workaround due to some error in getting conda to activate the environment. Original code I had was the following (its also commented in the ci.yml file if you want to try):
But this failed with the error: I tried lots of fixes for this, including reactivation of the shell, different ways of calling the conda activate function, etc. But nothing worked. Instead, I found a workaround where the
Its not ideal because this workaround requires existence of the |
The following changes are implemented: