-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Integration with virtualenvwrapper #1508
Comments
This seems an oversight on our side, indeed should be just |
gaborbernat
added a commit
that referenced
this issue
Jan 28, 2020
This is how things worked without the rewrite and in venv so consolidating. Signed-off-by: Bernat Gabor <[email protected]>
Resolved in #1509 |
Excellent - thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Congratulations on the rewrite.
I notice that
virtualenvwrapper
doesn't integrate with the new beta:Sure enough - I believe it is looking for a script
activate
- but the script file now depends on the shell -activate.sh
etc.It would be good if this could work somehow - would it be reasonable to create / link a default
activate
script for this case? Or should virtualenvwrapper be updated?The text was updated successfully, but these errors were encountered: