Zanie Blue
Zanie Blue
Hi! We're considering supporting that behavior yes, but we don't yet. Why is it important to you that the project itself isn't installed?
Installing the project itself is appropriate for both binaries and libraries though. I think we'll need more context on the use-case to make informed decisions here. `uv run python src/some_project/a.py`...
I think we can treat this as a duplicate of https://github.com/astral-sh/uv/issues/6460
And I think there's a pretty clear issue at https://github.com/astral-sh/uv/issues/6511 that tracks this use-case.
Can you share more details or examples please @CoolCat467?
Something like `--allow-variable ` might make sense for opt-in per-variable. We probably want to consider how we want the UX to work for lockfiles and credentials in general. I think...
This doesn't exist, but it might be feasible. I'd like to hear some more use-cases from other users first though, it seems hard to get right.
@BrendanJM lots of prior discussion about that, e.g., in https://github.com/astral-sh/uv/issues/1398 or https://github.com/astral-sh/uv/issues/4333 — sorry you're having trouble with it though. It's something we want to explore but it's _very_ hard.
Maybe? It seems okay to run in virtual or project environments, but weird for non-virtual environments.
`uv run jupyter` will fail unless you're in a project that requires `jupyter` or it is otherwise installed on your system, e.g., in the environment of the interpreter that uv...