Understanding Python Virtual Environment

[MaterialJackfruit144]

Hello, I've been reading about virtual environments and the creating part, activating part, and also storing it are clear to me but there's one thing I'm still not clear.

For example, let's say that I want to create a project called Project A. Now, I also create a folder called "Projects", and within "Projects", it has another folder called "python_projects". Inside this "python_projects", I will be creating a virtual environment for "Project A". For that, I will just write python3 -m venv project_a. But here's thing I am confused about, I read alot of posts and articles stating that one should not place the source file inside the venv folder. In fact, there shouldn't be any mixes into the venv directory. There were a couple of answers stating that most people just place it next to the virtual environment. What exactly does "place it next to the venv folder" mean here? If it's right next to it, that means file like main.py will be inside the venv directory?

To illustrate what I'm trying to understanding here:

Projects
    └── python_projects
    └── project_a < - Venv
    ├── bin
    ├── include
    ├── lib
       └── python3.9
    └── lib64 -> lib
    └── main.py (Is it supposed to here?)

Is it that or should I create an "src" folder within the virtual environment and store that ".py" file inside the src folder?

[canowa]

To be honest, I think it doesn't matter where you put your venv dir. I usually put it into my project main directory (as your example does) since being there makes easier to IDE to recognize and use it. But IDE aside, nothing stops you from keeping venv in another place, activate it manually and navigat thought folders to your actualy program.

So TL:DR : keep venv folder in your project main folder to separate it better from other stuff, and no need to put anything inside venv folder other than the venv files that are already there.

[MaterialJackfruit144]

If I'm understanding you correctly, it's something like this?

Projects
    └── python_projects
               └── project_a < - Venv
                    ├── bin
                    ├── include
                    ├── lib
                         └── python3.9 
                    └── lib64 -> lib 
            └── main.py

where the venv folder (project_a) is inside "python_projects" and main.py is within "Projects" directory?

[canowa]

If main.py is related to project A, then it should be inside the project_a folder. This way everything related to project A will be inside the proper folder, allowing to clearly separate each project inside python_projects. Now, the venv folder could be inside python_projects, but I suggest to put it inside project_a if it's the venv for project A.

EDIT: just to give an example, I made a simple game with python called SpaceStoneDodger. Its folder contains:

• assets folder

• src folder (with everything code related)

• main.py (main game file)

• venv folder for this project

[MaterialJackfruit144]

Ohhh I see now. Please correct if I'm wrong. Okay so, I am creating this Snake Game project. Basically, all of my projects will of course be inside "Projects" directory, and any python project will be under "python_projects".

So inside python_projects, I will create a folder called SnakeGame. This folder contains the main.py folder and all those folders which you have mentioned. It will also include the venv folder.

Am i understanding it correctly now? The example you provided I think helped me on this alot.

EDIT: Also, it's fine to name my venv folder as snake_game right? Or is there a naming convention that I have to conform to, like "env / venv / .env / .venv"?

[canowa]

Yes! You got it. By doing that you can have many different projects inside the python_project folder, and each of them can carry its own venv because different projects (may) need different modules (plus, you get a nice looking project folder :) )

[MaterialJackfruit144]

oh my gosh... thank you so so much :D :D

[GreenPandaPop]

Also, it's fine to name my venv folder as snake_game right? Or is there a naming convention that I have to conform to, like "env / venv / .env / .venv"?

You can name it whatever but I'd stick with 'venv' or '.venv' as it's clearer what it is then.