-
Notifications
You must be signed in to change notification settings - Fork 39
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
Docs: installing a development environment #1384
Comments
Related but different issue: #1383, in this other issue we address the fact that resolving for Python 3.9 (and 3.8, but not 3.10 and 3.11) would fail anyway. |
Where are we with this, do we recommend people to use conda i.e. doing something like:
It seems like @fabcor-maxiv mentioned that one could do it in one go using
I don't really have a strong opinion about it, but there is perhaps something I overlooked with this. It would be nice if we could update the documentation accordingly though :) |
I still want to investigate this, and I am open to input from others. I almost always use We could also simply remove this block from the documentation and let it to people to figure it out on their own if they need this. Maybe we should review why we added this block in the first place. |
This fixes the instructions for creating a development environment for a specific Python version. GitHub: fix mxcube#1384
This fixes the instructions for switching to a specific Python version in the development conda environment. GitHub: fix mxcube#1384
I am going with |
This fixes the instructions for switching to a specific Python version in the development conda environment. GitHub: fix mxcube#1384
https://mxcubeweb.readthedocs.io/en/latest/dev/environment.html#create-the-mxcubeweb-conda-environment
It mentions this command, but this is not a valid conda command:
There is no one-step way of doing this afaik. Hence this open issue: conda/conda#12313.
The text was updated successfully, but these errors were encountered: