FYI do NOT put your source code inside your #Python virtual environment. Editable installs are fine, but don't do something like py -m venv some_env and then put your code inside some_env as they canonical place to store it. Keep your virtual environment either as a subdirectory of your workspace or somewhere else entirely separate.
Pretend your virtual environment could be deleted at any moment if you need some guideline follow.
@brettcannon could you explain why? I was wondering about the automatic .gitignore. I never had issues doing this, but maybe I use it differently somehow?
@fschulze Because that directory is meant to be somewhat like a cache; look at how tools like tox, nox, etc. create and delete virtual environment constantly. Plus virtual environments are not designed to be relocatable or committed to version control. They are very much meant to be so lightweight you recreate them as needed (it's installation that typically takes a while).
@brettcannon none of that is a problem for me or a good argument. I can use git clean or rm -rf bin include lib and recreate the venv easily in place. For me it is much more convenient than having it some where else. I have the venv dirs in my .gitignore. I thin the automatically added one should do that instead of having * in it
@fschulze I don't appreciate the judgment that my argument is not a "good argument"; it's simply my argument and position and you're are welcome to disagree. But making a judgment of quality is not appreciated.
@EMR@brettcannon In the very very early days of virtual environments, the standard pattern was for environments to be long term, and for there to be a src directory inside the environment for your code. There may even be remnants of that pattern still in the code of some tools...
@pfmoore@EMR The problem we are seeing are people putting code directly into site-packages. My guess is people are reading tutorials about creating virtual environments, run pip, and then either through lack of further instruction or stop reading/watching, poke around, see where the .py files "live", and assume that's where their code goes as well.
Add comment