A one-liner for exporting your Conda environments for re-creation on another machine… but you might want to have a look at whether you actually need to recreate those environments.
for envs in $(conda env list | egrep -v "^#" | awk '{print $1}'); do echo "Exporting environment: $envs"; conda activate $envs; conda env export --no-builds | egrep -v "^prefix" > "$envs.yaml"; conda deactivate $envs; done; ls -l *.yaml
I've been thinking about myself as a coder a lot. I learnt #Python through its #Anaconda variety and #SpyderIDE. The course I initially went on used those, so I use them to write #SpatialAnalysis scripts.
However, I wonder whether I should learn what #JupyterNotebooks are about and potentially another IDE like #PyCharm or #VSCode / #VSCodium, but also actual software architecture and development things. Not to mention things like #Rstats, #RustLang, or #GoLang that interest me.
I really hope the future #Fedora web installer will be much more reliable & performant than what we've had for the past 10+ years, because I suffer everytime I need to use the current version of #Anaconda. It's just super fragile.
It randomly hangs, crashes or slugs around, whether you're trying to pick the language, set up network (for the netinstaller), and to use the partitioning tool (any of the three variants). Everytime I have to touch this Ming vase, I ponder my #Linux distro choices.
I have uninstalled and deleted all folders related to miniconda or anaconda, but every time I reinstall either and start JupyterLab, the launcher shows me Julia kernels and terminals that use the PowerShell of Windows instead of an anaconda prompt, and I cannot activate environments from there.
I just want my JupyterLab on Windows to work with Python and Julia, but I am not even trying with Julia now, they should be both uninstalled.
Still, I find empty files named python and python3 in AppData/Local/Microsoft/WindowsApps and I can't delete them with admin privileges.
What the hell
Time for the next step in the journey of our new installer!
The Workstation WG and Quality Team need your help testing the new Anaconda WebUI Installer. Testing runs from today to next Monday. Please follow the instructions below and give it a shot!
After that we'll need help with internationalization also for the F39 release (see below)
When you are starting a new #datascience project but you have to use windows and aren't allowed docker. And it crashes (see windows) and you forget to switch back to your environment to install the rest of the packages and mess up #anaconda base:
(Alt text here otherwise it deletes gif- Elen Rippley from alien: I say we take off and nuke it from orbit... It's the only way to be sure)
Antonio Cuni (#Anaconda Principal Software Engineer #PyScript#PyPy core developer #HPy founder) gave the talk "The CPU in your browser: WebAssembly demystified" at #PyConUS 2023 🇺🇲🐍