-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ModuleNotFoundError in pypy3.8 created with symlinked binary #2447
Comments
This is probably related to the changes introduced by @vfazio? |
oof. i'm not familiar with pypy at all but the driving force of #2441 was due to PEP405 which explicitly states that the "home" key should be the parent of the python binary: https://peps.python.org/pep-0405/#specification CPython handles this by recursing up the directories for landmark directories/files: https://github.com/python/cpython/blob/main/Modules/getpath.py#L208 Sorry that my PR broke functionality. I'm open to ideas here. |
Note that the "correct" value for |
I've checked also venv module in pypy3.8 and it's also not working with symlinked binary and
Both virtualenv and venv work if binaries are symlinked instead of copied. As far as I understand all these linked discussions and PEP405, I think that |
Closing per above, if upstream pypy changes behaviour we can revisit. |
Issue
I'm keeping all my python versions in
$HOME/bin
directory as symlinks. From 20.16.7 pypy3 virtualenvs created this way are not working properly:I've noticed that the
home
key inpyvenv.cfg
changed from a directory where symlinked python exists to a directory with a symlink. Changing this value to correct one fixed the issue with pypy.Environment
pip list
of the venv withvirtualenv
installed:Reproduction
Output of the virtual environment creation
The text was updated successfully, but these errors were encountered: