JP-2307: Edit README to avoid issues with default conda env and py3.10 #6411
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6411 +/- ##
=======================================
Coverage 78.52% 78.52%
=======================================
Files 408 408
Lines 34908 34908
=======================================
Hits 27413 27413
Misses 7495 7495
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report at Codecov.
|
README.md
Outdated
|
|
||
| ### Installing latest releases | ||
|
|
||
| You can install the latest released version via `pip`. From a bash/zsh shell: | ||
|
|
||
| conda create -n <env_name> python | ||
| conda create -n <env_name> python==3.9 |
There was a problem hiding this comment.
conda is a special flower and does not use the standard Python version comparison operators. What we really want here is a single =, not double, so that we get the latest python 3.9, i.e. 3.9.7 today. In Condaland, this is the same as specifying python~=3.9.0 using normal Python version comparison syntax.
| conda create -n <env_name> python==3.9 | |
| conda create -n <env_name> python=3.9 |
Update elsewhere as well.
There was a problem hiding this comment.
I see - tested the call, but didn't notice this wrinkle...
spacetelescope#6411) * Edit README * changelog * updates
spacetelescope#6411) * Edit README * changelog * updates
spacetelescope#6411) * Edit README * changelog * updates
Closes #6409
Resolves JP-2307
Description
This PR advises the creation of conda environments with python set to 3.9, to avoid build conflicts with the default python==3.10.0. This can be reverted once conflicts no longer exist.
Checklist