@publicvoit
Have you consulted this?:
imgs.xkcd.com/comics/python_en

Also, yeah that's why I just use virtualenvs for user projects and leave my system python environment alone. Messed that up too many times

@publicvoit I could see that being confusing. The way I use it is I have a virtualenv for most large projects. I tend to keep them all in "~/.venvs/$PROJECT". So I have a bunch of virtualenvs. Since that activate script is just changing environment variables you have to do it for each shell. I didn't think about doing it in your bashrc or something though. I think that would mess things up since sometimes you might need to interact with your system's python install

Follow

@jesse_m I found docs.python-guide.org/dev/virt which explained more things to me. So far, tutorials listed $project == virtualenvironment. However, the subdir "venv" (by convention) eases pain a lot.
My current issue with twine could be solved using a new environment via "virtualenv". Let's test some envs then... πŸ˜‰
Thanks for your support!

Β· Web Β· 1 Β· 0 Β· 0
Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!