-
Notifications
You must be signed in to change notification settings - Fork 562
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
VIRTUAL_ENV no longer used, giving "No Python default installation found in virtual environments" error #3765
Comments
I can second that. All my builds that use to work with 0.1.45 fail with this We do not use the |
Thanks for the report, this sounds like a regression from #3266. I think pointing to a system installation with What's the value of the |
@joennlae Could you share an example of the |
I can just share the name: Linting
on:
push:
branches:
- main
pull_request:
jobs:
checks:
runs-on: ubuntu-latest
name: ${{ matrix.quality-command }}
defaults:
run:
shell: bash -el {0}
strategy:
matrix:
quality-command:
- black
- ruff
- mypy
steps:
- uses: actions/checkout@v4
- name: Install environment
uses: conda-incubator/setup-miniconda@v3
with:
environment-file: environment.yml
activate-environment: 44ai
- name: Install Dependencies
run: |
conda activate 44ai
pip install uv==0.1.45
uv pip install -r requirements.txt
uv pip install -r requirements-dev.txt the name: 44ai
channels:
- defaults
dependencies:
- python=3.11
- tesseract
- ffmpeg I it is not the full environment but this should be reproducible. |
|
We could! |
@thundergolfer thanks for the details! Yeah this looks like an unintentional change but I think it's probably for the best if @joennlae looks like you're encountering the same as #3769 which I'm fixing in #3771 — we'll have that fixed asap. |
Yep thanks have made a PR internally to switch to |
@zanieb |
Hey @matmair — you're totally welcome and encouraged to use |
Neither VIRTUAL_ENV nor the --system flag seem to work on GitHub Actions anymore, switching back to pip |
Please share a reproduction if you can, I'm happy to help. |
The previous method of setting `VIRTUAL_ENV` was a hack and no longer works. See astral-sh/uv#3765 for more context.
We use
echo "VIRTUAL_ENV=${Python_ROOT_DIR}" >> $GITHUB_ENV
to avoid needing a virtual env in Github Actions. As of0.2.0
this has stopped working.python -m uv pip install -U pip setuptools wheel invoke
works so it does seem there's something going on with the Python installation detection.uv --version
is0.2.0
(latest)The text was updated successfully, but these errors were encountered: