-
Notifications
You must be signed in to change notification settings - Fork 84
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
Feature: support detection of existing virtual environments for a project #140
Comments
Hi there! I don't use pycharm so I'm not very aware of how it creates/stores its virtualenvs. Would you mind providing some information about the virtualenvs it creates? The following would definitely be useful:
|
With pycharm, the default is to create the virtual environment in a folder named venv (although it can be changed to whatever). Inside the venv folder, there is not a folder with the project name, only the venv files. For example:
When running mkvenv with
|
I kind of have the same issue as I use As a workaround, I currently use https://github.com/RobertDeRose/virtualenv-autodetect, but I would prefer using this plugin as it supports |
@MichaelAquilina, if I spend time trying to implement @escaped request and submit a PR, will you consider it, or is this something you don't want to see implemented in your script because it alters its current logic? |
@afeblot feel free to open a PR :) At the very least it provides us a better way of discussing the changes while also providing a branch for other users to test it out |
I use pycharm for development, so my virtual environments are created automatically when I make a new project. It would be really convenient if there was a function—maybe
addvenv
which created the.venv
file instead of prompting to create a whole new virtual environment.I know I can make the file myself, but it seems a little odd that the plugin is smart enough to detect a virtualenv, but won't allow you to add it.
The text was updated successfully, but these errors were encountered: