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

Pip doesn't work in pypy #177

Closed
vbabiy opened this issue Mar 15, 2011 · 3 comments
Closed

Pip doesn't work in pypy #177

vbabiy opened this issue Mar 15, 2011 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior

Comments

@vbabiy
Copy link
Contributor

vbabiy commented Mar 15, 2011

Pip currently requires that sys.prefix exist, which doesn't appear to be the case in Pypy (for some reason, it uses sys.pypy_prefix). This is fixed in this changeset: http://bitbucket.org/jasbaker/pip/changeset/7bc1620ecfd8


@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

  • Changed content.

Original Comment By: jasbaker

@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

Interesting. There are several other places where pip checks sys.prefix (in
util.py and req.py). If we really need to support sys.pypi_prefix as an
alternative, those places should also pull the value from locations.py, I
think. But this doesn't quite seem right; do we (and any other project that
uses sys.prefix for anything) have to support an alternative prefix attribute
for every non-CPython interpreter? Why can't PyPy set sys.prefix?


Original Comment By: Carl Meyer

@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

According to Alex Gaynor, a PyPy core dev, PyPy trunk now has sys.prefix, it
just didn't get in in time for the release. So all future releases of PyPy
should not have this problem. Accordingly, marking this wontfix.


Original Comment By: Carl Meyer

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant