Add some info about how to transition from Anaconda's default channel #2107
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| conda clean --all | ||
| ``` | ||
|
|
||
| 2. Create a zip archive of your conda installation. Use your favorite graphical tool |
There was a problem hiding this comment.
They can also use ls ~/.conda/environments.txt (and/or conda info --envs) to show their environments, so they can mv them somewhere safe and then put them back in place. Or we could list how to generate platform-specific lockfiles with conda list --explicit --md5 that they can then use to regenerate those envs.
There was a problem hiding this comment.
i'm mostly trying to keep it as simple as possible.
Many of these users are true users of conda, and not reallly developers of it, so these "tricks" make it seem more scary than anything.
Trying to "keep an environment alive" like this, and changing the the default environment, is likely going to be a huge problem when they type conda install ... any other package.
There was a problem hiding this comment.
I wonder if it is worth mentioning conda env export --from-history. It is probably a simple way to get a close-ish env file for existing environments without much magic or advanced directory/file browsing/moving.
There was a problem hiding this comment.
Added a little paragraph for both things without sacrificing the simplicity of the zip archive. Let me know what you think.
|
Nice! Let me know when you want a more thorough review. I just added a few comments that might be useful at this early stage. |
hmaarrfk
force-pushed
the
add_info_about_transition
branch
from
d70578a
to
59589d9
Compare
|
I'm a little confused with what changed over the months on the CIs and the pre-commit hook. how do i run |
|
pre-commit.ci autofix |
The Deploy Preview of |
|
Awesome. Some of the text really needs work but at least the infrastructure is there |
A common theme I see when helping users on github is that they have mixed packages from Anaconda + conda-forge. This really isn't the user's fault since I still remember the days that we had this as the recommended workflow. However, today this workflow leads to totally broken environments. I would like to document a guide that I can point them to and politely say: > Unfortunately this is no longer supported, see .... for how you can migrate.
Co-authored-by: jaimergp <[email protected]>
Co-authored-by: jaimergp <[email protected]>
for more information, see https://pre-commit.ci
hmaarrfk
force-pushed
the
add_info_about_transition
branch
from
b0bccc3
to
f95d42f
Compare
|
@jaimergp feel free to edit and push. I think if you "push" to the branch i'll be persuated to take your opinion. Keeping things simple is hard to balance. |
|
Thanks @hmaarrfk. I added a few things and edited a couple of terms for clarity. Take look and adjust whatever you think it's necessary. This is looking fine to merge, imo. |
Co-authored-by: Filipe <[email protected]>
|
Thanks all!!! |
A common theme I see when helping users on github is that they have mixed packages from Anaconda + conda-forge. This really isn't the user's fault since I still remember the days that we had this as the recommended workflow.
However, today this workflow leads to totally broken environments.
I would like to document a guide that I can point them to and politely say:
PR Checklist:
docs/, you have added it to the sidebar indocs/sidebar.json