Zanie Blue
Zanie Blue
For reference, they seem to be using our Python versions in the [Arch Linux package](https://gitlab.archlinux.org/archlinux/packaging/packages/uv/-/blob/21448fdf29b67b919b38a193abd5eb770222d4f1/PKGBUILD#L36-37).
> Shouldn't you be using mocks for this? What would we mock? Like.. create a several Python interpreters that report fake versions but make use of a single version behind...
To be clear, I would like to make it easy for you to package `uv` but I don't want to degrade our test suite to do it and we have...
I'll look into that and report back.
With https://github.com/astral-sh/uv/pull/2940 and https://github.com/astral-sh/uv/pull/2930 you should now be able to disable the very few tests that actually require specific patch versions. Thanks for your patience!
See also previous discussion at https://github.com/astral-sh/uv/issues/1386
Hi! I don't think we're willing to read another tool's configuration. We're still formalizing a policy around this though. We can also consider adding our own configuration section.
Yeah we'll have our own persistent configuration eventually, we're still determining what that will look like though. And yeah a pre-commit hook is of interest to us.
We are building persistent configuration right now, e.g. https://github.com/astral-sh/uv/pull/3007
I think different behavior for `-p 3.10` vs `-p python3.10` would be pretty confusing, I'd rather not introduce that.