Zanie Blue

I started looking into this.... we probably want to avoid building from source each time but pyenv does not support linking a system Python version without a plugin (ref https://github.com/pyenv/pyenv/issues/1244)....

@CharString Sorry I'm not sure how that accomplishes our goal here? We want to make sure that people using `pyenv` have correct behavior with `uv`. The complexity here is avoiding...

> ...however, there is no need to support older versions of dependencies, and testing in a matrix is often too resource-intensive. Consequently, there is little reason to test with older...

TIL! This sounds good to me as a great Python 3.12 milestone although I do not think it should be enabled by default.

Great point, it may not be worth prioritizing until then since there will be many false negatives

Related - https://github.com/astral-sh/uv/issues/13131 - https://github.com/astral-sh/uv/issues/14504 I think Charlie's comment on the latter one sums up our stance > It could make sense to support it, it's just a matter of...

I think we'll probably want a separate argument, e.g., `--exclude-package`, to avoid disambiguating between paths and names? In general, I think we want this functionality for constraints, excludes, and overrides...

We generally can't use space delimited names in the CLI because it creates ambiguous parsing. We usually prefer `,`. There are various places where we allow this (and I'd expect...

It's not intended for `--no-install-project` to be persistent. Why does `uv run` reinstall the package? The logs should indicate the reason the current one is not seen as valid. Does...

This is cool to see! I'm happy to help unblock ya'll with changes to `setup-uv`, `python-build-standalone`, and `uv` if necessary.