Zanie Blue
Zanie Blue
I guess let's go for it and we can deal with it if there are problems. We could collapse the checksums into a single file if we have to, yeah....
This makes sense to me. As a minor note, we allow exporting the `uv.lock` file to a `requirements.txt` file and some people want to commit both (https://github.com/astral-sh/uv-pre-commit/issues/16). When adding `uv.lock`...
@Czaki it looks like this has some unrelated changes in it now.
You're welcome to contribute to the documentation; its source is all here. We're not likely to have a wiki — I don't see what benefit we'd get from separating that...
Thanks for the report. I think @charliermarsh has some context on this.
We explicitly don't allow installing packages into the managed Python installation environments.
Because they're only intended to be sources for creating virtual environments. We are trying to move away from mutable global state.
Perhaps our [Docker guide](https://docs.astral.sh/uv/guides/integration/docker/#using-the-environment) would be helpful to demonstrate how to setup a system-wide environment.
You can still do that, you just need to put create a virtual environment and put it on the path (as described in the linked guide). Is there a reason...
I'm not sure I really understand your point, why isn't this sufficient: ``` uv venv export VIRTUAL_ENV="$(pwd)/.venv" export PATH="$VIRTUAL_ENV/bin:$PATH" ```