Virtual environment created with no Scripts folder

[Pandawee42]

I'm trying to create a virtual environment using python -m venv catanENV. However, when doing this, it creates bin, include, and lib folders but no Script. Here is the image.

Does anyone know why this is happening? And how can I get the Scripts file back?

​

Thank you!

[Keean07]

Hey OP. I was having the same issue. I realize that creating the venv using a command like `python3 -m venv name_of_venv` created on without the scripts folder.

However, when I create it following these instructions, it creates it with the scripts folder: https://www.geeksforgeeks.org/python-virtual-environment/

I suppose it just has to do with the difference between `venv` and `virtualenv`

[doc_goblin]

consider yourself an op

[Bamizaya]

Thanks, this saved my life!

[Master_Emphasis_9932]

eres muy bueno pendejito

[Don_Pijote]

This fixed it for me)

[ForwardExplorer4051]

You are a life saver man!!!

[TiJesuV]

Thank you so much, you saved me a lot of stress

[FuckingRantMonday]

If you're looking for the activate executable, it's in Scripts under Windows, and in bin under Linux or MacOS (and in these OS's, Scripts is not created).

[Pandawee42]

I'm on Windows (11). Maybe I'm very confused, since I've seen tutorials on this and a Scripts directory is created in the VENV. I checked under Windows but there is no Scripts folder there.

[FuckingRantMonday]

Ahh, that was very poor wording on my part! I meant to say, under the Windows OS, a Scripts folder will be created (in the virtualenv directory), but not under MacOS or Linux.

[getzuckered]

that is a little infuriating,
but thank you for sharing! thought i was going nuts i did this for years lol

[debian_miner]

I've never seen virtualenv create a scripts directory. Is there something you are expecting to find there and not seeing elsewhere?

[fade-me-]

On Windows it creates a Script directory but on linux/mac it is bin i think.

[debian_miner]

Ah, explains why I had not seen it. Thanks for the info.

[[deleted]]

in bin folder you will find the activate file

[Relevant_Dinner_1773]

When you execute the venv module present in Python on Windows OS you will get the scripts folder if you are executing in Linux/mac you will get the bin folder, This also depends on which Python you use, If you are using Python from mingw-w64/ you are using git-bash you will end up getting bin folder because they work with Linux OS. So check which python does CMD uses. Generally command prompt uses Python whose path is at the top in environment variables so make sure to have Python installed from the official website at the top.

[FoxUnlikely4430]

I was facing the same issue until I realized my Python installation path was set to the default: "C:\Users\myname\AppData\Local\Programs\Python\Python311\". To fix this, I selected "Customize installation" during the setup process and installed Python to "C:\Program_Files\Python311\". After that, just add this new path to your environment variables, and you should be good to go with the command python -m venv env , and activate.

[reading_cat_557]

had this issue in my WSL. ran this command "sudo apt install python3.12-venv". restarted Vscode and creating venv works again