-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Please use the default virtualenv directory #214
Comments
Yeah, respecting |
If you activate the virtualenv before you use poetry, poetry will use your existing virtual environment. Also, |
Like @valignatev said, it would be cooler if poetry played nice with virtualenv(wrapper) and respects the already existing environment. If there is no WORKON_HOME set, keep using that cache folder. Sounds like a good idea! |
|
Reposting that doesn’t make it better. A new virtualenv created by poetry will not work with other vitualenv tools. That’s bad! Why break an otherwise cool and working standard? It’s a much better user experience working with poetry if it just respects existing virtalenv settings. |
You said:
It already does... it just doesn't support using |
I'm not familiar with the As @bertjwregeer said, Poetry already uses existing virtual environments. About the path, you can configure it with |
@cauebs I know that at least virtualenvwrapper and pipenv understand |
@valignatev |
Okay, i can bend poetry so that it works the way it should to not disrupt the workflow of new users. But I thought poetry wants to be better?! And that means to not annoy users if there is no good reason to it. Respecting WORKON_HOME by default: happy users |
Hmm... Maybe there are benefits to keeping Poetry's virtual environments separated from the rest. Python tooling and its userbase are more complex than they might seem initially. Remember:
I think this is a discussion worth having, but I definitely wouldn't be ready to rule out the current approach. |
In case anyone's counting, I'm in the "respect |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Well i now have auto activation of the projects .venv folder active and dont need the above, so this might be closed. |
With Poetry version 1.0.10 this works:
|
…en calling set_constraint() (python-poetry#214)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
rather than that custom /Users/andy/Library/Caches/pypoetry/virtualenvs directory.
Currently all virtualenv(wrapper) command dont work due to the bad virtualenv home. :(
Other than that and the other ticket (#213) i like poetry - just switched from pipenv.
The text was updated successfully, but these errors were encountered: