Thanks! The hardest part for me is to remember the various commands. I only very rarely create a new Python project and each time I have to reboot my brain/memory as to how it all works. Either it's a challenge of plainly remembering the commands, or it's a challenge of finding previous commands in the bash history, or it's a challenge of remembering where I wrote my notes on how to use it.
The tech isn't particularly important. It's more important about the cognitive challenge for things one doesn't do on a daily basis.
But it's good to know that there exists a project that can help with more versions and stuff. I've been lucky over the last couple of years on *not* having to worry about testing on multiple versions of Node. But once that changes again, I'll seriously consider asdf as a possible contender to other pure-Node based solutions.
Hi Peter, I have enjoyed using pyenv for a long time, what I liked most for deployed python stuff is that since the app now has its own python, one does not risk issues when suddenly the OS package manager updates the OS python to a new version. The local version will always stay the same until you decide to run the app with a different version.
Over xmas I started to play with a full version handler, asdf. For python it does the same as pyenv, but it has the huge advantage of also handling a ton of other languages and tools in the same way through plugins, so I would recommend you to take a look and see if it could be something for you if you enjoy pyenv.
One thing that took me a while to figure out with asdf and python before I got to work as smooth as pyenv is that if you want to use venvs within python to keep your installed pips separate and such. After installing a python version, you also need to install your preferred python venv handler(-s) in every python version, I use virtualenvwrapper, but it's the same regardless of your venv handler of choice. Then it works smoothly! I have now migrated my env to use asdf instead of pyenv.
https://github.com/asdf-vm/asdf
Comment
Thanks!
The hardest part for me is to remember the various commands. I only very rarely create a new Python project and each time I have to reboot my brain/memory as to how it all works. Either it's a challenge of plainly remembering the commands, or it's a challenge of finding previous commands in the bash history, or it's a challenge of remembering where I wrote my notes on how to use it.
The tech isn't particularly important. It's more important about the cognitive challenge for things one doesn't do on a daily basis.
But it's good to know that there exists a project that can help with more versions and stuff. I've been lucky over the last couple of years on *not* having to worry about testing on multiple versions of Node. But once that changes again, I'll seriously consider asdf as a possible contender to other pure-Node based solutions.
Parent comment
Hi Peter, I have enjoyed using pyenv for a long time, what I liked most for deployed python stuff is that since the app now has its own python, one does not risk issues when suddenly the OS package manager updates the OS python to a new version. The local version will always stay the same until you decide to run the app with a different version. Over xmas I started to play with a full version handler, asdf. For python it does the same as pyenv, but it has the huge advantage of also handling a ton of other languages and tools in the same way through plugins, so I would recommend you to take a look and see if it could be something for you if you enjoy pyenv. One thing that took me a while to figure out with asdf and python before I got to work as smooth as pyenv is that if you want to use venvs within python to keep your installed pips separate and such. After installing a python version, you also need to install your preferred python venv handler(-s) in every python version, I use virtualenvwrapper, but it's the same regardless of your venv handler of choice. Then it works smoothly! I have now migrated my env to use asdf instead of pyenv. https://github.com/asdf-vm/asdf