gwilikers@lemmy.ml to Linux@lemmy.ml · 8 hours agoYour Most Frustrating Configuration Experience?message-squaremessage-square39fedilinkarrow-up121arrow-down10file-text
arrow-up121arrow-down1message-squareYour Most Frustrating Configuration Experience?gwilikers@lemmy.ml to Linux@lemmy.ml · 8 hours agomessage-square39fedilinkfile-text
minus-squareJustTestingAlinkfedilinkarrow-up2·edit-25 hours agopyenv and pyenv-virtualenv together solves this for me. Virtualenv with specific python versions that work together well with other tools like pip or poetry. It boils down to something like $ pyenv install 3.12.7 $ pyenv virtualenv 3.12.7 myenv $ pyenv activate myenv and at that point you can do regular python stuff like pip installing etc.
minus-squareJubilantJaguar@lemmy.worldlinkfedilinkarrow-up1·1 hour agoIf you’re having to type out version numbers in your commands, something is broken. I ended up having to roll my own shell script wrapper to bring some sanity to Python.
pyenv and pyenv-virtualenv together solves this for me. Virtualenv with specific python versions that work together well with other tools like pip or poetry.
It boils down to something like
$ pyenv install 3.12.7 $ pyenv virtualenv 3.12.7 myenv $ pyenv activate myenv
and at that point you can do regular python stuff like pip installing etc.
If you’re having to type out version numbers in your commands, something is broken.
I ended up having to roll my own shell script wrapper to bring some sanity to Python.