Zanie Blue
Zanie Blue
It looks like this is a duplicate of https://github.com/astral-sh/uv/issues/1586 which is now tracked in https://github.com/astral-sh/uv/issues/4130 You need to run `pyenv rehash` to add the shims. We opened an upstream issue...
Cool idea! I wonder if we could do something like create a dedicated shell script for this that does something like... 1) Checks if you have uv installed, if not,...
Or, as discussed on Discord, we should just create the lock file without a `--locked` option.
@Eh2406 you may be interested in https://github.com/astral-sh/uv/pull/6154 — to get started, I'm implementing the collapse on the derivation tree instead of in the resolver.
Ah this sounds quite nice.
You can use `--raw-sources` to avoid adding a lower bound. Thanks for the praise. cc myself #5605 — we should cover this in the project concept documentation if we don't...
This is also not covered in the `--raw-sources` reference documentation. @charliermarsh should we consider an easier name for this too? `--raw-sources` doesn't feel intuitive. Should it just be `--raw`?
Yeah, we can support this.
If `pyenv` puts executables on the PATH, we'll find them, but we don't support querying pyenv-specific locations or pyenv itself. Details on what we support at https://docs.astral.sh/uv/concepts/python-versions/#discovery-of-python-versions