-
Notifications
You must be signed in to change notification settings - Fork 935
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
uv-managed python installed into .local/bin can't be used with venv module #8821
Comments
This is known and reported upstream: astral-sh/python-build-standalone#380 |
See also #8429 |
I'm running into this; uv-installed python symlinked into |
see astral-sh/uv#8821 for more info. It causes the signing step to fail since that creates its own virtualenv. Signed-off-by: Gary Oberbrunner <[email protected]>
I think |
Sadly, that doesn't work:
|
Alas, if you use Annoyingly, it works in isolation which makes it hard to inspect:
|
I ended up prepending the actual python bin dir to $PATH. That seems to work for me. Details at AcademySoftwareFoundation/openfx@8276ac8 if anyone’s interested. |
uv 0.4.30
python3.12 -m venv
fails to create a virtual environment.Steps how I reproduced this problem. Using
3.12.6
to use a version that was not already installed.Let's try execute the python in the venv:
Is the symlink in the virtual environment resolved? (no)
The text was updated successfully, but these errors were encountered: