Closed tjnewton closed 3 years ago
Thanks for that catch @tjnewton! That is really helpful - This is also a useful reminder that I need to test and package this up for Python 3.9 - I hadn't realised that the default conda python had bumped!
Because I want this to appear in the docs ASAP I'm going to re-base this to master, and merge into develop from there. Sorry to be a pain - hopefully I can do this without needing you to change anything.
Sounds good. I'm happy to tweak it if needed. I'm looking forward to giving EQcorrscan a whirl!
Bugger, I can't - @tjnewton can you make this change on a branch from master please? Or if it is annoying I can close this and make one myself?
Let me know which way you want to go - I'm also keen to see your name go on the contributors list if you want.
Bugger, I can't - @tjnewton can you make this change on a branch from master please? Or if it is annoying I can close this and make one myself?
Let me know which way you want to go - I'm also keen to see your name go on the contributors list if you want.
No problem, I will make the change now.
What does this PR do?
This PR adds a python version to the command to create a conda environment in the installation doc.
Why was it initiated? Any relevant Issues?
Default behavior initiates a conda environment with Python 3.9, which yields a conflict when installing EQcorrscan via conda with
conda install -c conda-forge eqcorrscan
:PR Checklist
develop
base branch selected?CHANGES.md
.CONTRIBUTORS.md
.