5 ms·

Pls dont. Just install several pythons with different binary names. ex. python3.8, python3.9, python3.11 No need to complicate things. If using Poetry, you

• scriptme 2y ago
  Here's all the project boilerplate you need with pyenv when working on a new project. > $ pyenv install 3.8 > $ pyenv local 3.8 > $ python3 -m venv .venv > $ source .venv/bin/activate and you're done. Not really sure what you might consider difficult about pyenv, but it's just a tool to instigate your python venvs which is a built tool for most modern versions of python.
  • 0x008 2y ago
    > Not really sure what you might consider difficult about pyenv - compiling from source - need to install build-essentials on docker images which takes up lot of space and takes a long time
• Hackbraten 2y ago
  What do you do when (not if) your system package manager eventually drops that Python version from their core repositories? The good thing about pyenv is that it makes you rely less on package maintainers. You can come back to your Python project 10 years later and have a real chance that it still works, even if you have changed workstations in between.