You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
creating venv in: /tmp/venv-create-bug-example.pj058eb3
Traceback (most recent call last):
...
subprocess.CalledProcessError: Command
'['/tmp/venv-create-bug-example.pj058eb3/bin/python', '-m', 'ensurepip', '--upgrade', '--default-pip']'
returned non-zero exit status 127.
subprocess stdout:
b'/tmp/venv-create-bug-example.pj058eb3/bin/python:
error while loading shared libraries:
/tmp/venv-create-bug-example.pj058eb3/bin/../lib/libpython3.12.so.1.0:
cannot open shared object file: No such file or directory\n'
...
Obviously, this is because the python binary links against libpython*.so dynamically with a relative path, and there no longer is a libpython*.so at this path when the Python executable (or a symlink to it) finds itself in the venv.
Minimal example:
Running this with a python-build-standalone binary that has a shared library dependency on
libpython*.so
, e.g.cpython-3.12.7+20241016-x86_64-unknown-linux-gnu-install_only
will make this fail with (extra newlines inserted for readability):Obviously, this is because the
python
binary links againstlibpython*.so
dynamically with a relative path, and there no longer is alibpython*.so
at this path when the Python executable (or a symlink to it) finds itself in the venv.See also the corresponding issue in uv:
The text was updated successfully, but these errors were encountered: