-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optionally using a path and naming virtual environment file #8
Comments
I didn't hear about '~/virtualenvs/' usage before therefore not sure about integrating this feature. Is it widely used? |
Well. The "~/virtualenvs" style usage is not too wide but I am sure it's something being used. But ".venv" is more widely used as virtualenvs is not something you generally upload to anywhere or share. It's pretty logical to keep it as a "hidden" folder. At least it is surely a personal choice more than a public rule ( again it most of the time will only stay on the developers' device). I am planning on making a pull request for the change, since it will basically be a default value with an option to change it. And it should simply be a string change. I just don't have the time right now. |
Got it. Thaks for your contribution. Assigning this issue to you. Not closing the issue until any pr is created. 🎉 |
There are different conventions for virtual environments.
Like creating all the virtual environments on a folder ( "~/virtualenvs/" ),
or naming the virtual environment with a leading dot ( ".../project/path/.venv" ),
right now the virtual environment is created inside the project folder with a default name "venv"
The text was updated successfully, but these errors were encountered: