We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 pip install manim_automata
error: Failed to locate a virtualenv or Conda environment (checked: VIRTUAL_ENV, CONDA_PREFIX, and .venv). Run uv venv to create a virtualenv.
VIRTUAL_ENV
CONDA_PREFIX
.venv
uv venv
my dev env is a devcontainer, specifically the image mcr.microsoft.com/devcontainers/python:1-3.12-bullseye hosted at https://github.com/devcontainers/images/blob/main/src/python
I think .venv is useful to contain python dev envs, but in my case, the whole OS is contained. I shouldn't have to use .venv
The text was updated successfully, but these errors were encountered:
Thanks, this is already supported -- you can pass --system or a specific Python interpreter with --python path/to/python. See the docs here: https://github.com/astral-sh/uv?tab=readme-ov-file#installing-into-arbitrary-python-environments.
--system
--python path/to/python
Sorry, something went wrong.
But wait, --system doesn't work in GitHub codespaces
If you don't have permissions to write to the system (as in GitHub codespaces) you should just create a virtual environment.
You can track --user support (which would be an alternative) in #2077
--user
Yep, I am already tracking that one
No branches or pull requests
error: Failed to locate a virtualenv or Conda environment (checked:
VIRTUAL_ENV
,CONDA_PREFIX
, and.venv
). Runuv venv
to create a virtualenv.my dev env is a devcontainer, specifically the image mcr.microsoft.com/devcontainers/python:1-3.12-bullseye hosted at https://github.com/devcontainers/images/blob/main/src/python
I think .venv is useful to contain python dev envs, but in my case, the whole OS is contained. I shouldn't have to use .venv
The text was updated successfully, but these errors were encountered: