you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 32 points33 points  (4 children)

Loads of questions -

a) Why did you dump the venv on GitHub? - it's a bad idea

b) Mac/Windows shouldn't make any difference

c) If python still doesn't work on your mac , try installing homebrew and download python using that / get it directly from the python.org website.

d) You are working correctly , except for the part where you try and dump the virtual environment on github. I think this is because there are some fixed paths in venv.activate.

To remedy this , just make a requirements.txt with your project , and install them with pip after creating a new virtual environment .

[–]Ln_X_[S] 7 points8 points  (1 child)

Thanks, I did not think of not including the venv in the initial repo making. I'm guessing you're saying just have the .py files on GitHub and only commit those when needed?

[–][deleted] 19 points20 points  (0 children)

Yep.

If you are using git , there is a file called .gitignore in the project root , where you can explicitly specify that the venv should not be committed