Carl Meyer <[email protected]> added the comment: Conclusions from discussion on IRC today:
1) In the long term, it would be good for PyPy to emulate CPython layout more closely and eliminate the special PyPy distutils install scheme. 2) In the short term, because virtualenv already hardcodes the PyPy scheme, this change would break use of PyPy with existing virtualenv releases. 3) It might be possible to make the scheme transition in future without a hard break if virtualenv first implements https://github.com/pypa/virtualenv/issues/416, and versions of virtualenv using get_python_lib gain wide traction. In the very short term (for the PyPy 2.0 release), the attached patch at least fixes the "home" and "user" schemes, without making any changes to the default use of pypy scheme. This does not yet fix virtualenv issues 302 and 306 (or pip 625), but it does fix pip issues 624 and 629. ---------- nosy: +carljm -pjenvey status: unread -> chatting ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1272> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
