Optionally using a path and naming virtual environment file
shubidubapp opened this issue · 3 comments
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"
I didn't hear about '~/virtualenvs/' usage before therefore not sure about integrating this feature. Is it widely used?
As you know general approach for creating virtualenv(ofc it is not a rule) is creating a folder called 'venv' inside the project and that's why flask-now act like this.
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. 🎉