Zanie Blue
Zanie Blue
Not right now. What would you use it for?
See `python_executables_from_search_path` for the current implementation.
Considering if this is the correct approach still. We should also test with the `pyenv-virtualenv` shim.
I find this implementation awkward as I only want this to be used if it's a virtual environment interpreter but we can't easily enforce that in `python_executables`. I'll probably poke...
I'd appreciate input on a better approach here.
@charliermarsh yeah this is still necessary if we want to support detecting virtual environments that are only activated by an executable shim. I'm not in love with the implementation though.
This is the intended behavior — upgrading changes the locked version within the constraints you provide in your pyproject.toml: https://docs.astral.sh/uv/concepts/projects/#upgrading-locked-package-versions It'd be weird for us to change the specification of...
Makes sense to me.
Hi! Do you mind reading these to see if they address your questions? - https://docs.astral.sh/uv/pip/compatibility/#packages-that-exist-on-multiple-indexes - https://docs.astral.sh/uv/reference/settings/#index-strategy - https://docs.astral.sh/uv/configuration/authentication/#custom-ca-certificates
Interesting, that all looks correct.