-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
feat: virtualenv improvements #389
Conversation
I think more or less the same as https://github.com/justjanne/powerline-go/pull/387/files right? |
That one does not look at |
...except that I won't :) The implementation here falls back to the venv dir even if loading the pyvenv.cfg fails for some reason. For example, does it exist in all venv dirs, e.g. ones created by old versions of |
When I get a chance I'll compare our changes, we can probably just merge them into one PR since they're both related. 👍 |
any chance of getting this merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall, though
Standard venv activation typically sets it to `(name) `. Parse that first to avoid having to parse pyvenv.cfg. Co-authored-by: Janne Mareike Koschinski <[email protected]>
3241c1b
to
ef5e672
Compare
Some virtualenv improvements, see individual commits for details.