Zanie Blue
Zanie Blue
That would be the idea, yeah. Though for `uv run example.py` I think we'll re-use a cached environment.
e.g. ``` ❯ uv venv venv Using Python 3.12.1 Creating virtualenv at: venv Activate with: source venv/bin/activate ❯ uv pip install httpx --python ./venv Resolved 7 packages in 207ms Installed...
It's sort of mentioned in https://docs.astral.sh/uv/concepts/python-versions/#requesting-a-version — we could add a note where you linked but it's not mentioned there because that section is about _using_ the packages in the...
👍 @derek-pyne you can also use ``` [tool.uv] constraint-dependencies = ["llvm>0.43.0"] ``` to add a constraint without adding it as a dependency of your project.
Thanks for engaging with the project! Specifically, you would like us to read `.env` files before every operation? Or something else?
I'm going to mark this as not-planned for now. We may revisit in the future. If people have additional use-cases or thoughts please feel free to share!
Willing to consider this further, i.e., we'd read it in `uv run` only.
> Or is this not necessary anymore with uv run (sorry for my ignorance, I haven't really used uv much yet)? It shouldn't be needed if you use `uv run`,...
Thank you! I wonder what the `pipx` invocation for Jupyter is?
😬 Yeah that's pretty wild too. Thanks for sharing!