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

Be able to run an unmodified virtualenv #1357

Merged
merged 3 commits into from
Sep 10, 2016
Merged

Conversation

kmod
Copy link
Collaborator

@kmod kmod commented Sep 6, 2016

Well, really an unmodified pip+setuptools

The last piece is py_compile. Just shim that back into our parser
to get the parser to write out a pyc file.

It seems like we don't even need this -- most callers of py_compile
(or at least, virtualenv), don't seem to care if the compile step
passed or failed. But while we're here, try to support it.

@kmod kmod force-pushed the unmodified_venv branch 2 times, most recently from de9aa13 to add3040 Compare September 6, 2016 22:22
Well, really an unmodified pip+setuptools

The last piece is py_compile.  Just shim that back into our parser
to get the parser to write out a pyc file.

It seems like we don't even need this -- most callers of py_compile
(or at least, virtualenv), don't seem to care if the compile step
passed or failed.  But while we're here, try to support it.
Do it by patching distutils, which setuptools I guess builds on
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant