Skip to content
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

Unset __PYVENV_LAUNCHER__ on macOS to avoid virtualenv weirdness #28663

Merged
merged 1 commit into from
Apr 28, 2021

Conversation

foolip
Copy link
Member

@foolip foolip commented Apr 23, 2021

Exactly how this all works isn't clear, but since the fix in
python/cpython#9516 was to simply hide the
environment variable from the interpreter it seems reasonably safe.

Fixes #27377.

Exactly how this all works isn't clear, but since the fix in
python/cpython#9516 was to simply hide the
environment variable from the interpreter it seems reasonably safe.

Fixes #27377.
Copy link
Contributor

@jgraham jgraham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally I'd like @gsnedders to look at this, but if it works that seems fine.

@foolip
Copy link
Member Author

foolip commented Apr 28, 2021

I need this to do anything in WPT and don't want to keep applying it locally, so I'll merge and hope this isn't going to blow up in my face :)

@foolip foolip merged commit b2c62f3 into master Apr 28, 2021
@foolip foolip deleted the foolip/__PYVENV_LAUNCHER__ branch April 28, 2021 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Virtualenv-provided pip3 doesn't work on macOS
3 participants