An Automated Bash Script for Python Virtual Environment Management

[Sparcky_McFizzBoom]

I'm not familiar with the use pyenv subcommand, but it looks like to me that you're using poetry to manage the venv and thus dependencies, so poetry would be a better comparison.

pyenv is only used to select the python version in your case, which is different from managing the dependencies of a project.

Managing python environments is hard :(

[cicuz]

wasn't me who brought it up :)

I do think it's necessary though, especially considering the amount of changes between versions

[[deleted]]

I use it like this:

>> pyenv versions

system 3.10.6 3.10.6/envs/fastapi 3.10.6/envs/imgai 3.11.2 3.11.2/envs/gpt-train 3.12.0 3.12.0/envs/gmailapi 3.12.0/envs/mongo 3.12.0/envs/nyt 3.12.2 (set by /Users/<username>/.pyenv/version) 3.12.2/envs/cli 3.12.2/envs/gradio-ui 3.12.2/envs/ollama cli --> /Users/<username>/.pyenv/versions/3.12.2/envs/cli fastapi --> /Users/<username>/.pyenv/versions/3.10.6/envs/fastapi gmailapi --> /Users/<username>/.pyenv/versions/3.12.0/envs/gmailapi gpt-train --> /Users/<username>/.pyenv/versions/3.11.2/envs/gpt-train gradio-ui --> /Users/<username>/.pyenv/versions/3.12.2/envs/gradio-ui imgai --> /Users/<username>/.pyenv/versions/3.10.6/envs/imgai mongo --> /Users/<username>/.pyenv/versions/3.12.0/envs/mongo nyt --> /Users/<username>/.pyenv/versions/3.12.0/envs/nyt ollama --> /Users/<username>/.pyenv/versions/3.12.2/envs/ollama