fix_lib64 breaks pypy #302

hukka opened this Issue Jul 10, 2012 · 7 comments

8 participants

$ pypy --distribute my_new_envpypy
Traceback (most recent call last):
  File "", line 51, in run_toplevel
  File "", line 2429, in <module>
  File "", line 942, in main
  File "", line 1043, in create_environment
    site_packages=site_packages, clear=clear))
  File "", line 1167, in install_python
  File "", line 1535, in fix_lib64
    "Unexpected python lib dir: %r" % lib_dir)
AssertionError: Unexpected python lib dir: 'my_new_envpypy'

Commenting line 1167, disabling the use of the fix_lib64 function, fixes this.


Same here, using Slackware64.


pretty sure this is related to #306.
virtualenv is not handling how pypy breaks the mold for it's lib and site-packages locations.
both of these issues could probably be handled in one pull.

might make an attempt at this.


Same for Fedora 18.


+1 Same issue here. Any workarounds?


Same for Fedora 20...

bes@besnik-pc pi$ virtualenv --version
bes@besnik-pc pi$ pypy --version
Python 2.7.3 (6c8420e89b80b4c90720115e31c2793ba7fff08d, Nov 19 2013, 13:04:31)
[PyPy 2.2.0 with GCC 4.8.2 20131017 (Red Hat 4.8.2-1)]

Just in case anybody stumbles over this: I had the same problem with version 1.8.4, and then upgraded to version 1.11.4 and the problem seems to be fixed now.

So I think this issue can be closed.

Python Packaging Authority member

Cheers @treo . If anyone still encounters the issue on latest virtualenv, please feel free to comment or reopen.

@Ivoz Ivoz closed this Apr 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment