Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement PEP 440-compliant local version semantics #8797

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Implement PEP 440-compliant local version semantics #8797

merged 1 commit into from
Nov 6, 2024

Conversation

ericmarkmartin
Copy link
Contributor

@ericmarkmartin ericmarkmartin commented Nov 4, 2024 •
edited by charliermarsh
Loading

Summary

Implement a full working version of local version semantics. The (AFAIA) major move towards this was implemented in #2430. This added support such that the version specifier torch==2.1.0+cpu would install [email protected]+cpu and consider [email protected]+cpu a valid way to satisfy the requirement torch==2.1.0 in further dependency resolution.

In this feature, we more fully support local version semantics. Namely, we now allow torch==2.1.0 to install [email protected]+cpu regardless of whether [email protected] (no local tag) actually exists.

We do this by adding an internal-only Max value to local versions that compare greater to all other local versions. Then we can translate torch==2.1.0 into bounds: greater than 2.1.0 with no local tag and less than 2.1.0 with the Max local tag.

Test Plan

Depends on astral-sh/packse#227.

@ericmarkmartin ericmarkmartin marked this pull request as draft November 4, 2024 06:07
@ericmarkmartin
Copy link
Contributor Author

@charliermarsh I took a stab at this. I didn't spend a ton of time testing but I think it's maybe right? If it is, the main issue here might be performance---after this change, == bounds get translated into a bounded range rather than a singleton, and the upper bound of the range has a local version (the Max sentinel value) so it has to be a VersionFull. This is maybe a bit sad for the number of slow comparisons it introduces. Maybe there's a way to encode the local version sentinel in VersionSmall such that we don't have to suffer this?

@charliermarsh
Copy link
Member

On first glance I think this approach makes a lot of sense? Clever! I need to review it more closely though, and we should indeed add something to VersionSmall to capture the sentinel, I think.

@charliermarsh
Copy link
Member

I will poke around at this, if that's cool -- see if I can get it passing.

@charliermarsh charliermarsh self-assigned this Nov 4, 2024
@ericmarkmartin
Copy link
Contributor Author

Poke away! I took a whirl at trying to detect the weird synthesized bounds with the local version max and rewriting it back to a normal-looking equality in report.rs but didn't have much luck

@charliermarsh
Copy link
Member

👍 I think I know how to solve it, or at least have some ideas.

@ericmarkmartin
Copy link
Contributor Author

ericmarkmartin commented Nov 4, 2024 •
edited
Loading

Another thing to think about--do we still want the #2430 mechanism? I don't think we need it after this change, but it's also clearly not hurting us. I could imagine it's still a good perf optimization but I'm not familiar enough with the resolver to make a claim either way

@charliermarsh
Copy link
Member

Did you link to the wrong PR? Heh

@charliermarsh
Copy link
Member

Maybe you're thinking of the version selection mechanism where we check if we're requesting an exact-equals version?

@ericmarkmartin
Copy link
Contributor Author

Did you link to the wrong PR? Heh

Indeed! I mixed up #2340 and #2430--whoops! I edited it in the comment above

@charliermarsh
Copy link
Member

I almost have tests passing.

@charliermarsh charliermarsh force-pushed the local-version-semantics branch 3 times, most recently from 3320a26 to d082763 Compare November 4, 2024 20:39
@ericmarkmartin
Copy link
Contributor Author

Nice! I realize that I used LocalVersion::Max but LocalVersionSlice::Sentinel---do you have a preference?

@charliermarsh
Copy link
Member

Probably a minor preference for Max because it's similar to the "max" we use elsewhere in Version.

@charliermarsh
Copy link
Member

Next I will try tearing out all the special-casing around local versions.

@charliermarsh
Copy link
Member

(I'll stop force-pushing to this branch and merge from now on so we can collab.)

@charliermarsh
Copy link
Member

I need to update Packse to change some of the auto-generated scenario expectations.

@charliermarsh
Copy link
Member

I think the main thing missing here is a few more Packse tests (I can write) plus a solution to the VersionFull thing.

@charliermarsh
Copy link
Member

@ericmarkmartin -- Do you think it's possible for us to somehow reuse the max / SUFFIX_MAX concept that already exists on VersionSmall? It's already "the version after all local versions".

@charliermarsh
Copy link
Member

Do you think it's possible for us to somehow reuse the max / SUFFIX_MAX concept that already exists on VersionSmall? It's already "the version after all local versions".

I think not, because we don't want foo==1.0.0 to match 1.0.0.post1.

@charliermarsh charliermarsh marked this pull request as ready for review November 5, 2024 01:47
@charliermarsh charliermarsh changed the title WIP: local version semantics Implement PEP 440-compliant local version semantics Nov 5, 2024
@BurntSushi
Copy link
Member

For context on VersionSmall, its purpose is to compactly represent Version values that are the most frequently occurring. Versions with local segments are specifically infrequent relative to the universe of all versions used (on PyPI at least), and so using VersionSmall to represent them is probably not that impactful.

@ericmarkmartin
Copy link
Contributor Author

ericmarkmartin commented Nov 5, 2024 •
edited
Loading

For context on VersionSmall, its purpose is to compactly represent Version values that are the most frequently occurring.

Right, but if you change VersionSmall like Charlie describes above, then you have 2.5 bytes to encode a local version tag, so you may as well use it for something right? I guess there's some way you could make a specific encoding for LocalVersion::Max without following the existing scheme?

Versions with local segments are specifically infrequent relative to the universe of all versions used (on PyPI at least)

Yeah, the spec even says

Local version identifiers SHOULD NOT be used when publishing upstream projects to a public index server

@charliermarsh
Copy link
Member

Yeah I messaged Andrew about this -- I think we're all aligned on reclaiming some of the "version suffix" bits so that we can encode this special-case local tag.

@BurntSushi
Copy link
Member

@ericmarkmartin I think we need just one bit that we can pull from the version suffix. We definitely don't want to take more than that because the version suffix is where things like 10 in .dev10 get stored. If we devoted all of the suffix to local segments, we'd be giving up a "small" representation for something that is much more common than things with a local segment.

I'm going to put up a PR with a slight refactor that I think should make this change easier.

@charliermarsh
Copy link
Member

Doing the VersionSmall changes now but it'll be a separate PR.

@charliermarsh charliermarsh mentioned this pull request Nov 5, 2024
Merged
@ericmarkmartin
Copy link
Contributor Author

ericmarkmartin commented Nov 5, 2024 •
edited
Loading

@BurntSushi I was mistakenly thinking we were reclaiming the extra bit so we could have a 4 bit discriminant. Then we'd have "local" as a possible value for said discriminant, hence my thinking we had 2.5 bytes to work with for the local segment in that case.

I now realize we're talking about just stealing the bit as an orthogonal indicator of the local sentinel, which makes way more sense. Sorry for my confusion

@charliermarsh charliermarsh changed the base branch from main to tracking/050 November 6, 2024 03:03
@charliermarsh
Copy link
Member

(Starting the process of merging these into the v0.5 branch.)

@charliermarsh charliermarsh merged commit a3cfe72 into astral-sh:tracking/050 Nov 6, 2024
62 of 63 checks passed
charliermarsh added a commit that referenced this pull request Nov 6, 2024
@charliermarsh
Remove all special-casing for local version identifiers (#8818)
c0dde3c 
## Summary

After #8797, we have spec-compliant
handling for local version identifiers and can completely remove all the
special-casing around it.
charliermarsh added a commit that referenced this pull request Nov 6, 2024
@charliermarsh
Incorporate [max] local version into VersionSmall (#8843)
8f109f4 
## Summary

See discussion in #8797.
charliermarsh pushed a commit that referenced this pull request Nov 6, 2024
@ericmarkmartin @charliermarsh
Implement PEP 440-compliant local version semantics (#8797)
3d1f25f 
## Summary

Implement a full working version of local version semantics. The (AFAIA)
major move towards this was implemented in #2430. This added support
such that the version specifier `torch==2.1.0+cpu` would install
`[email protected]+cpu` and consider `[email protected]+cpu` a valid way to satisfy
the requirement `torch==2.1.0` in further dependency resolution.

In this feature, we more fully support local version semantics. Namely,
we now allow `torch==2.1.0` to install `[email protected]+cpu` regardless of
whether `[email protected]` (no local tag) actually exists.

We do this by adding an internal-only `Max` value to local versions that
compare greater to all other local versions. Then we can translate
`torch==2.1.0` into bounds: greater than 2.1.0 with no local tag and
less than 2.1.0 with the `Max` local tag.

## Test Plan

Depends on astral-sh/packse#227.
charliermarsh added a commit that referenced this pull request Nov 6, 2024
@charliermarsh
Remove all special-casing for local version identifiers (#8818)
a491503 
## Summary

After #8797, we have spec-compliant
handling for local version identifiers and can completely remove all the
special-casing around it.
charliermarsh added a commit that referenced this pull request Nov 6, 2024
@charliermarsh
Incorporate [max] local version into VersionSmall (#8843)
90672e9 
## Summary

See discussion in #8797.
@zanieb zanieb mentioned this pull request Nov 7, 2024
Merged
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@ericmarkmartin @zanieb
Implement PEP 440-compliant local version semantics (#8797)
9270dd3 
Implement a full working version of local version semantics. The (AFAIA)
major move towards this was implemented in #2430. This added support
such that the version specifier `torch==2.1.0+cpu` would install
`[email protected]+cpu` and consider `[email protected]+cpu` a valid way to satisfy
the requirement `torch==2.1.0` in further dependency resolution.

In this feature, we more fully support local version semantics. Namely,
we now allow `torch==2.1.0` to install `[email protected]+cpu` regardless of
whether `[email protected]` (no local tag) actually exists.

We do this by adding an internal-only `Max` value to local versions that
compare greater to all other local versions. Then we can translate
`torch==2.1.0` into bounds: greater than 2.1.0 with no local tag and
less than 2.1.0 with the `Max` local tag.

Depends on astral-sh/packse#227.
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@charliermarsh @zanieb
Remove all special-casing for local version identifiers (#8818)
93d7563 
After #8797, we have spec-compliant
handling for local version identifiers and can completely remove all the
special-casing around it.
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@charliermarsh @zanieb
Incorporate [max] local version into VersionSmall (#8843)
cbba56b 
See discussion in #8797.
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@ericmarkmartin @zanieb
Implement PEP 440-compliant local version semantics (#8797)
c49c7bd 
Implement a full working version of local version semantics. The (AFAIA)
major move towards this was implemented in #2430. This added support
such that the version specifier `torch==2.1.0+cpu` would install
`[email protected]+cpu` and consider `[email protected]+cpu` a valid way to satisfy
the requirement `torch==2.1.0` in further dependency resolution.

In this feature, we more fully support local version semantics. Namely,
we now allow `torch==2.1.0` to install `[email protected]+cpu` regardless of
whether `[email protected]` (no local tag) actually exists.

We do this by adding an internal-only `Max` value to local versions that
compare greater to all other local versions. Then we can translate
`torch==2.1.0` into bounds: greater than 2.1.0 with no local tag and
less than 2.1.0 with the `Max` local tag.

Depends on astral-sh/packse#227.
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@charliermarsh @zanieb
Remove all special-casing for local version identifiers (#8818)
90653e1 
After #8797, we have spec-compliant
handling for local version identifiers and can completely remove all the
special-casing around it.
zanieb pushed a commit that referenced this pull request Nov 7, 2024
@charliermarsh @zanieb
Incorporate [max] local version into VersionSmall (#8843)
70f8377 
See discussion in #8797.
@BrewTestBot BrewTestBot mentioned this pull request Nov 8, 2024
Merged
@ericmarkmartin ericmarkmartin deleted the local-version-semantics branch November 8, 2024 04:35
@pradyunsg
Copy link

Coming here from the 0.5.0 changelog entry: this is quite smart!

@apoorvkh apoorvkh mentioned this pull request Nov 12, 2024
Merged
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Nov 18, 2024
@tmeijn
build(deps): update astral-sh/uv to v0.5.2
4d35963 
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [astral-sh/uv](https://github.com/astral-sh/uv) | minor | `0.4.24` -> `0.5.2` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>astral-sh/uv (astral-sh/uv)</summary>

### [`v0.5.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#052)

[Compare Source](astral-sh/uv@0.5.1...0.5.2)

##### Enhancements

-   Hide `--no-system` from `uv pip tree` CLI ([#&#8203;9040](astral-sh/uv#9040))
-   Allow configuration of Python and PyPy install mirrors in `uv.toml` ([#&#8203;8695](astral-sh/uv#8695))
-   Allow passing Python download mirrors to `uv python install` ([#&#8203;8695](astral-sh/uv#8695))
-   Add support for specifying conflicting extras and dependency groups ([#&#8203;8976](astral-sh/uv#8976), [#&#8203;9096](astral-sh/uv#9096))
-   Consistent colon usage in build failure errors ([#&#8203;8994](astral-sh/uv#8994))
-   Show full derivation chain when encountering build failures ([#&#8203;9108](astral-sh/uv#9108))
-   Show link we failed on parsing index pages ([#&#8203;9118](astral-sh/uv#9118))
-   Remove duplicate log when searching for interpreters ([#&#8203;9092](astral-sh/uv#9092))
-   Update uv development status classifier to "Stable" on PyPI ([#&#8203;8943](astral-sh/uv#8943))
-   Use rich diagnostic formatting for early build failures ([#&#8203;9041](astral-sh/uv#9041))
-   Use rich diagnostic formatting for install failures ([#&#8203;9043](astral-sh/uv#9043))

##### Performance

-   Avoid retraversing filesystem when testing exact glob matches ([#&#8203;9022](astral-sh/uv#9022))

##### Bug fixes

-   Allow `--no-build` to validate lock ([#&#8203;9024](astral-sh/uv#9024))
-   Allow default indexes to be marked as explicit ([#&#8203;8990](astral-sh/uv#8990))
-   Avoid creating `.venv` in `uv add --frozen` and `uv add --no-sync` ([#&#8203;8980](astral-sh/uv#8980))
-   Avoid duplicating first-entry comments in `uv add` ([#&#8203;9109](astral-sh/uv#9109))
-   Defer reporting of build failures in resolver ([#&#8203;9098](astral-sh/uv#9098))
-   Fix references to `--resolution-strategy` in error message output ([#&#8203;8971](astral-sh/uv#8971))
-   Ignore virtual environments in parent directories when choosing Python version for new projects ([#&#8203;9075](astral-sh/uv#9075))
-   Forward SIGTERM to child processes in `uv run` ([#&#8203;8933](astral-sh/uv#8933))
-   Prefer Python executable names that match the request over default names ([#&#8203;9066](astral-sh/uv#9066))
-   Prefer compatible to incompatible distributions when packages exist on multiple indexes ([#&#8203;8961](astral-sh/uv#8961))
-   Publish: Ignore non-matching files ([#&#8203;8986](astral-sh/uv#8986))
-   Revert `uv.lock` changes when `uv add` fails ([#&#8203;9030](astral-sh/uv#9030))
-   Show file extensions on available commands when not `.exe` ([#&#8203;9099](astral-sh/uv#9099))
-   Sort by name, then specifiers in `uv add` ([#&#8203;9097](astral-sh/uv#9097))
-   Split after specifiers in `--with` requirements ([#&#8203;9089](astral-sh/uv#9089))
-   Support multiple extras in universal pip compile output ([#&#8203;8960](astral-sh/uv#8960))

##### Preview features

-   Build backend: Add tests for source tree -> source dist -> wheel conversions ([#&#8203;9091](astral-sh/uv#9091))
-   Build backend: Switch to custom `glob-walkdir` implementation ([#&#8203;9013](astral-sh/uv#9013))
-   Build backend: Add minimal wheel settings ([#&#8203;9085](astral-sh/uv#9085))

##### Documentation

-   Add wget instructions for systems without curl ([#&#8203;8630](astral-sh/uv#8630))
-   Fix `.env` file example in docs ([#&#8203;9064](astral-sh/uv#9064))
-   Fix reference to `--resolution` in docs ([#&#8203;8968](astral-sh/uv#8968))
-   Fix typo in GitLab integration docs ([#&#8203;9047](astral-sh/uv#9047))
-   Update format of environment variable reference ([#&#8203;9018](astral-sh/uv#9018))
-   Use Python syntax for `value_type` consistently ([#&#8203;9017](astral-sh/uv#9017))
-   Use `[[index]]` API in configuration example ([#&#8203;9065](astral-sh/uv#9065))
-   Mention how to use extras ([#&#8203;8972](astral-sh/uv#8972))
-   Add some words about specifying conflicting extras/groups ([#&#8203;9120](astral-sh/uv#9120))

### [`v0.5.1`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#051)

[Compare Source](astral-sh/uv@0.5.0...0.5.1)

##### Enhancements

-   Allow installation of manylinux wheels on `riscv64` ([#&#8203;8934](astral-sh/uv#8934))

##### Bug fixes

-   Build source distributions at top-level of cache ([#&#8203;8905](astral-sh/uv#8905))
-   Allow non-registry dependencies in `uv pip list --outdated` ([#&#8203;8939](astral-sh/uv#8939))
-   Compute superset of existing and required hashes when healing cache ([#&#8203;8955](astral-sh/uv#8955))
-   Enable uv to replace and delete itself on Windows ([#&#8203;8914](astral-sh/uv#8914))
-   Remove source distribution filename from cache ([#&#8203;8907](astral-sh/uv#8907))
-   Respect `--index-url` in `uv pip list` ([#&#8203;8942](astral-sh/uv#8942))
-   Respect comma-separated extras in `--with` ([#&#8203;8946](astral-sh/uv#8946))

##### Documentation

-   Add uninstall note for previous versions ([#&#8203;8937](astral-sh/uv#8937))
-   Remove some missed references to `~/.cargo/bin` ([#&#8203;8936](astral-sh/uv#8936))
-   Split README's install code block into 3 ([#&#8203;8853](astral-sh/uv#8853))

### [`v0.5.0`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#050)

[Compare Source](astral-sh/uv@0.4.30...0.5.0)

Since the launch of Python version, project, and tool management capabilities back in August, we've seen extraordinary adoption of uv. We've been iterating rapidly: adding new features, fixing bugs, and improving the user experience. Despite moving quickly, stability and compatibility have been a major focus — we've made thirty releases since our last breaking change. Consequently, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.

##### Breaking

-   **Use base executable to set virtualenv Python path** ([#&#8203;8481](astral-sh/uv#8481))

    Previously, uv canonicalized the path to the Python executable when setting the Python path in created virtual environments. This behavior had several undesirable effects: it would bypass stabilized version directories (as constructed by Homebrew) and it was not consistent with the Python standard library's behavior. Now, uv uses the `sys._base_executable` path.
-   **Use XDG (i.e. `~/.local/bin`) instead of the Cargo home directory in the installer** ([#&#8203;8420](astral-sh/uv#8420))

    Previously, uv's installer used `$CARGO_HOME` or `~/.cargo/bin` for its target install directory. It's been a longstanding complaint that uv uses this directory, as there's no relationship to Cargo. Now, uv will be installed into `$XDG_BIN_HOME`, `$XDG_DATA_HOME/../bin`, or `~/.local/bin` (in that order). Note that `$UV_INSTALL_DIR` can always be used to override the target directory.
-   **Discover and respect `.python-version` files in parent directories** ([#&#8203;6370](astral-sh/uv#6370))

    Previously, uv only read `.python-version` files from the working directory. Now, uv will check parent directories for `.python-version` files; however uv will not search for `.python-version` files beyond project boundaries. The new behavior is better aligned with that of `pyenv` and Rye.
-   **Error when disallowed settings are defined in `uv.toml`** ([#&#8203;8550](astral-sh/uv#8550))

    Some settings can only be defined in the `pyproject.toml`. Previously, uv would ignore these settings when present in the `uv.toml`. Now, uv will error to avoid confusion about why the settings are not respected.
-   **Implement PEP 440-compliant local version semantics** ([#&#8203;8797](astral-sh/uv#8797))

    Previously, uv's implementation of local versions (e.g. `2.0+cpu`) was not compliant with the specification due to the technical complexity of implementing the local version semantics in the PubGrub algorithm. Thanks to the work of [@&#8203;ericmarkmartin](https://github.com/ericmarkmartin), uv now has a spec-compliant implementation. Namely, uv will now allow a request for `torch==2.1.0` to install `[email protected]+cpu` regardless of whether `[email protected]` (without a local tag) actually exists.
-   **Treat the base Conda environment as a system environment** ([#&#8203;7691](astral-sh/uv#7691))

    Previously, uv would not distinguish between the base and other Conda environments. Now, uv uses `CONDA_DEFAULT_ENV` and the names `base` and `default` to determine if an environment active via `CONDA_PREFIX` is the base environment. If the base environment is active, the `--system` flag must be used to mutate it.
-   **Do not allow pre-releases when the `!=` operator is used** ([#&#8203;7974](astral-sh/uv#7974))

    Previously, uv would use the presence of a pre-release specifier in a version specifier as an opt-in to allow pre-release versions during resolution. The new behavior does not allow pre-releases when an inequals operator is used, e.g., `!= 2.0a1`.
-   **Prefer `USERPROFILE` over `FOLDERID_Profile` when selecting a home directory on Windows** ([#&#8203;8048](astral-sh/uv#8048))

    This change is a side-effect of switching from the `directories` crate to `etcetera` for determining canonical system paths. If `USERPROFILE` is not set, the behavior will be unchanged.
-   **Improve interactions between color environment variables and CLI options** ([#&#8203;8215](astral-sh/uv#8215))

    Previously, uv would respect the `FORCE_COLOR` and `NO_COLOR` environment variables over the `--color` flag. Now, when the `--color` flag is explicitly provided, uv will respect it over the environment variables.
-   **Make `allow-insecure-host` a global option** ([#&#8203;8476](astral-sh/uv#8476))

    Previously, this option was only available in some parts of uv. Now, `--allow-insecure-host` can be provided to any command. For consistency, the `allow-insecure-host` setting has been removed from the `[tool.uv.pip]` configuration in favor of `[tool.uv]`.
-   **Only write `.python-version` files during `uv init` for workspace members if the version differs** ([#&#8203;8897](astral-sh/uv#8897))

    Previously, uv would create a `.python-version` file for workspace members during `uv init`. Now, uv will only do so if the version differs from the `.python-version` file in the workspace root since uv will respect `.python-version` files in parent directories.

##### Enhancements

-   Add `uv tree --outdated` ([#&#8203;8893](astral-sh/uv#8893))
-   Add armv8l alias for armv7l to support arm 32-bit compatibility mode ([#&#8203;8881](astral-sh/uv#8881))
-   Add support for `pip list --outdated` ([#&#8203;8872](astral-sh/uv#8872))
-   Allow semicolons directly after direct URLs ([#&#8203;8836](astral-sh/uv#8836))
-   Enable support for arbitrary git transports ([#&#8203;8769](astral-sh/uv#8769))
-   Improve Python discovery source messages ([#&#8203;8890](astral-sh/uv#8890))
-   Show dedicated error for trailing `;` on URL and path requirements ([#&#8203;8835](astral-sh/uv#8835))
-   Add progress bar for `uv cache clean` ([#&#8203;8857](astral-sh/uv#8857))
-   Warn on failure to query system configuration file ([#&#8203;8829](astral-sh/uv#8829))

##### Preview features

-   Add support for building basic source distributions with the experimental uv build backend ([#&#8203;8886](astral-sh/uv#8886))

##### Bug fixes

-   Respect dynamic version updates in `uv lock` ([#&#8203;8867](astral-sh/uv#8867))
-   Respect fork markers in `--resolution-mode=lowest-direct` ([#&#8203;8839](astral-sh/uv#8839))

##### Documentation

-   Add further examples of git+https support ([#&#8203;8841](astral-sh/uv#8841))
-   Add installer variables to environment reference ([#&#8203;8874](astral-sh/uv#8874))
-   Add note on private classifier ([#&#8203;8783](astral-sh/uv#8783))
-   Update pip-and-uv strictness example ([#&#8203;8822](astral-sh/uv#8822))
-   Fix `uv python install` docs to use an existing PyPy version ([#&#8203;8845](astral-sh/uv#8845))
-   Document how to mimic `--verbose` with `RUST_LOG` ([#&#8203;8858](astral-sh/uv#8858))

### [`v0.4.30`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0430)

[Compare Source](astral-sh/uv@0.4.29...0.4.30)

##### Enhancements

-   Add support for `.env` and custom env files in `uv run` ([#&#8203;8811](astral-sh/uv#8811))
-   Add support for `--all-packages` in `uv run`, `uv sync`, and `uv export` ([#&#8203;8742](astral-sh/uv#8742), [#&#8203;8741](astral-sh/uv#8741), [#&#8203;8739](astral-sh/uv#8739))
-   Allow use of `--frozen` with `--all-packages` in `uv sync` and `uv export` ([#&#8203;8760](astral-sh/uv#8760))
-   Show full error chain on tool upgrade failures ([#&#8203;8753](astral-sh/uv#8753))
-   Add `--check-url` to `uv publish` to check for existing distributions during upload ([#&#8203;8531](astral-sh/uv#8531))
-   Suggest using `--check-url` when `--skip-existing` is used ([#&#8203;8803](astral-sh/uv#8803))

##### Bug fixes

-   Allow incompatible `requires-python` for source distributions with static metadata ([#&#8203;8768](astral-sh/uv#8768))
-   Allow managed downloads with `--python-preference system` ([#&#8203;8808](astral-sh/uv#8808))
-   Avoid error for `--group` defined in non-root workspace member ([#&#8203;8734](astral-sh/uv#8734))
-   Avoid showing dependency group annotations on workspace members in tree ([#&#8203;8730](astral-sh/uv#8730))
-   Do not error when the Python bin directory is missing on `uv python uninstall` ([#&#8203;8725](astral-sh/uv#8725))
-   Include member groups when locking workspace ([#&#8203;8736](astral-sh/uv#8736))
-   Fix bug where `python_version < '0'` could appear in a final resolution ([#&#8203;8759](astral-sh/uv#8759))
-   Sanitize filenames during zip extraction ([#&#8203;8732](astral-sh/uv#8732))
-   Switch to RFC 9110 compatible format for exclude newer requests ([#&#8203;8752](astral-sh/uv#8752))

##### Preview features

-   Add support for installing versioned Python executables on Windows ([#&#8203;8663](astral-sh/uv#8663))
-   Improve interactions with existing Python executables during install ([#&#8203;8733](astral-sh/uv#8733))

##### Rust API

-   Extend `BaseClient` to accept extra middleware ([#&#8203;8807](astral-sh/uv#8807))
-   Add `From` for `FlatDistributions` struct ([#&#8203;8800](astral-sh/uv#8800))

##### Documentation

-   Fix environment variable name in providing credentials section ([#&#8203;8740](astral-sh/uv#8740))
-   Fix `add httpx` example with real git branch ([#&#8203;8756](astral-sh/uv#8756))
-   Fix indentation in `projects.md` ([#&#8203;8772](astral-sh/uv#8772))
-   Fix link to publish guide in `README` ([#&#8203;8720](astral-sh/uv#8720))
-   Generate environment variables documentation from code ([#&#8203;8493](astral-sh/uv#8493))
-   Improve and fix some documents ([#&#8203;8749](astral-sh/uv#8749))
-   Improve environment variables document ([#&#8203;8777](astral-sh/uv#8777))

### [`v0.4.29`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0429)

[Compare Source](astral-sh/uv@0.4.28...0.4.29)

##### Enhancements

-   Sort errors during display in `uv python install` ([#&#8203;8684](astral-sh/uv#8684))
-   Update resolver to use disjointness checks instead of marker equality ([#&#8203;8661](astral-sh/uv#8661))
-   Add `riscv64` to supported Python platform tags ([#&#8203;8660](astral-sh/uv#8660))

##### Bug fixes

-   Fix hard and soft float libc detection for managed Python distributions on ARM ([#&#8203;8498](astral-sh/uv#8498))
-   Handle cycles in `uv pip tree` ([#&#8203;8689](astral-sh/uv#8689))
-   Respect dependency group markers in `uv export` ([#&#8203;8659](astral-sh/uv#8659))
-   Support transitive dependencies in Git workspaces ([#&#8203;8665](astral-sh/uv#8665))
-   Use portable paths for subdirectories in lock URLs ([#&#8203;8707](astral-sh/uv#8707))
-   Update `uv init --virtual` to imply `--no-package` ([#&#8203;8595](astral-sh/uv#8595))

##### Preview

-   Install versioned Python executables into the bin directory during `uv python install` (Unix only) ([#&#8203;8458](astral-sh/uv#8458))

##### Documentation

-   Clarify relationship between specifiers and `requires-python` range ([#&#8203;8688](astral-sh/uv#8688))
-   Fix broken link in docs ([#&#8203;8552](astral-sh/uv#8552))
-   Fix outdated documentation on `Requires-Python` ([#&#8203;8679](astral-sh/uv#8679))
-   Add Google Artifact Registry index authentication guide ([#&#8203;8579](astral-sh/uv#8579))

### [`v0.4.28`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0428)

[Compare Source](astral-sh/uv@0.4.27...0.4.28)

##### Enhancements

-   Add support for requesting free-threaded builds via `+freethreaded` ([#&#8203;8645](astral-sh/uv#8645))
-   Improve trusted publishing error messages ([#&#8203;8633](astral-sh/uv#8633))
-   Remove unneeded `return` from Maturin project template ([#&#8203;8604](astral-sh/uv#8604))
-   Skip Python interpreter discovery for `uv export` ([#&#8203;8638](astral-sh/uv#8638))
-   Hint about missing trusted publishing permission ([#&#8203;8632](astral-sh/uv#8632))

##### Configuration

-   Add environment variable to disable progress output ([#&#8203;8600](astral-sh/uv#8600))

##### Bug fixes

-   Fork when minimum Python version increases ([#&#8203;8628](astral-sh/uv#8628))
-   Ignore empty groups when validating lock ([#&#8203;8598](astral-sh/uv#8598))
-   Remove duplicate word in error message ([#&#8203;8589](astral-sh/uv#8589))
-   Support cyclic dependencies in `uv tree` ([#&#8203;8564](astral-sh/uv#8564))
-   Update `uv init` to imply `--package` when using `--build-backend` ([#&#8203;8593](astral-sh/uv#8593))
-   Restore use of `dev-dependencies` and `requires-dev` for lockfile compatibility ([#&#8203;8599](astral-sh/uv#8599))

##### Documentation

-   Clarify `requires-python` requirement for dependencies ([#&#8203;8619](astral-sh/uv#8619))
-   Update CLI documentation for `--cache-dir` ([#&#8203;8627](astral-sh/uv#8627))

### [`v0.4.27`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0427)

[Compare Source](astral-sh/uv@0.4.26...0.4.27)

This release includes support for the `[dependency-groups]` table as recently standardized in [PEP 735](https://peps.python.org/pep-0735/). The table allows for declaration of optional dependency groups that are not published as part of the package metadata, unlike `[project.optional-dependencies]`. There are new `--group`, `--only-group`, and `--no-group` options throughout the uv interface.

Previously, uv used a single `tool.uv.dev-dependencies` list for declaration of development dependencies. Now, uv supports declaring development dependencies in a standardized format and allows splitting development dependencies into multiple groups.

For compatibility, and to simplify usage for people that do not need multiple groups, uv special-cases the group named `dev`. The `dev` group is equivalent to `tool.uv.dev-dependencies`. The contents of `tool.uv.dev-dependencies` will merged into the `dev` group in uv's resolver. The `--dev`, `--only-dev`, and `--no-dev` flags remain as aliases for the corresponding `--group` options. Support for `tool.uv.dev-dependencies` remains in this release, but will display warnings in a future release.

uv syncs the `dev` group by default — this matches the exististing behavior for `tool.uv.dev-dependencies`. The default groups can be changed with the `tool.uv.default-groups` setting.

Thank you to Stephen Rosen who authored PEP 735.

##### Enhancements

-   Support for PEP 735 ([#&#8203;8272](astral-sh/uv#8272))
-   Add support for `--dry-run` mode in `uv lock` ([#&#8203;7783](astral-sh/uv#7783))
-   Don't allow non-string email in authors ([#&#8203;8520](astral-sh/uv#8520))
-   Enforce lockfile schema versions ([#&#8203;8509](astral-sh/uv#8509))

##### Bug fixes

-   Always attach URL to network errors ([#&#8203;8444](astral-sh/uv#8444))
-   Fix dangling non-platform dependencies in `uv tree` ([#&#8203;8532](astral-sh/uv#8532))
-   Prefer `lto` over `debug` free-threaded managed Python builds ([#&#8203;8515](astral-sh/uv#8515))

##### Documentation

-   Add `tool.uv.sources` to the "Settings" reference ([#&#8203;8543](astral-sh/uv#8543))
-   Add reference to `uv build` and `uv publish` in the landing pages ([#&#8203;8542](astral-sh/uv#8542))
-   Avoid duplicate `[tool.uv]` header in TOML examples ([#&#8203;8545](astral-sh/uv#8545))
-   Document `.netrc` environment variable and path ([#&#8203;8511](astral-sh/uv#8511))
-   Fix `.netrc` typo in authentication docs ([#&#8203;8521](astral-sh/uv#8521))
-   Fix heading level of "Script support" on docs landing page ([#&#8203;8544](astral-sh/uv#8544))
-   Move the installation configuration docs to a separate page ([#&#8203;8546](astral-sh/uv#8546))
-   Update docs for `--publish-url` to avoid duplication. ([#&#8203;8561](astral-sh/uv#8561))
-   Fix typo ([#&#8203;8554](astral-sh/uv#8554))
-   Fix typo in description of `--strict` flag ([#&#8203;8513](astral-sh/uv#8513))

### [`v0.4.26`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0426)

[Compare Source](astral-sh/uv@0.4.25...0.4.26)

##### Enhancements

-   Allow static dependency metadata entries for direct URL requirements ([#&#8203;7846](astral-sh/uv#7846))
-   Use reinstall report formatting for `uv python install --reinstall` ([#&#8203;8487](astral-sh/uv#8487))
-   Add support for system-level `uv.toml` configuration ([#&#8203;7851](astral-sh/uv#7851))

##### Bug fixes

-   Apply `requires-python` narrowing with upper bounds ([#&#8203;8403](astral-sh/uv#8403))
-   Avoid rewriting `[[tool.uv.index]]` entries when credentials are provided ([#&#8203;8502](astral-sh/uv#8502))
-   Fix `uv add` comment handling for empty arrays ([#&#8203;8504](astral-sh/uv#8504))
-   Replace dashes with underscores in index credential variables ([#&#8203;8452](astral-sh/uv#8452))
-   Respect `--allow-insecure-host` in `uv publish` ([#&#8203;8440](astral-sh/uv#8440))
-   Allow arbitrary `--package` includes in `uv tree` ([#&#8203;8507](astral-sh/uv#8507))
-   Remove existing Python install after successful download in `uv python install` ([#&#8203;8485](astral-sh/uv#8485))

##### Documentation

-   Add docs example for URLs with `[tool.uv.dependency-metadata]` ([#&#8203;8484](astral-sh/uv#8484))
-   Add help page for build failures ([#&#8203;8286](astral-sh/uv#8286))
-   Fix `cache-keys` typo in `tags = true` ([#&#8203;8422](astral-sh/uv#8422))
-   Add documentation examples for manual branch, rev, and tag Git dependencies ([#&#8203;8497](astral-sh/uv#8497))

##### Error messages

-   Improve error message for cache info serialization ([#&#8203;8500](astral-sh/uv#8500))
-   Suggest `--from` command when executable is available for `uvx` ([#&#8203;8473](astral-sh/uv#8473))
-   Support `--with-editable` in `uv tool install` ([#&#8203;8472](astral-sh/uv#8472))

### [`v0.4.25`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0425)

[Compare Source](astral-sh/uv@0.4.24...0.4.25)

##### Enhancements

-   Add support for `uv pip show --files` ([#&#8203;8369](astral-sh/uv#8369))
-   Don't prefetch unreachable packages ([#&#8203;8246](astral-sh/uv#8246))
-   Remove `tool.uv.sources` table if it is empty ([#&#8203;8365](astral-sh/uv#8365))
-   Modify cache versioning to support backwards compatibility ([#&#8203;8386](astral-sh/uv#8386))

##### Configuration

-   Add support for `UV_FROZEN` and `UV_LOCKED` ([#&#8203;8340](astral-sh/uv#8340))

##### Bug fixes

-   Allow dashes and underscores in custom index names ([#&#8203;8339](astral-sh/uv#8339))
-   Avoid panic when Git dependencies are included in fork markers ([#&#8203;8388](astral-sh/uv#8388))
-   Check existing source by normalized name before `uv add` and `uv remove` ([#&#8203;8359](astral-sh/uv#8359))
-   Fix bug where username from authentication cache could be ignored ([#&#8203;8345](astral-sh/uv#8345))
-   Fix to respect comments positioning in pyproject.toml on change ([#&#8203;8384](astral-sh/uv#8384))
-   Redact index sources in `uv.lock` ([#&#8203;8333](astral-sh/uv#8333))
-   Use correct indentation when project table contains open bracket comment ([#&#8203;8387](astral-sh/uv#8387))
-   Only remove a source from `[tool.uv.sources]` if it is no long being referenced ([#&#8203;8366](astral-sh/uv#8366))
-   Modify `uv pip list` and `uv tree` to print to stdout regardless of `--quiet` flag ([#&#8203;8392](astral-sh/uv#8392))

##### Error messages

-   Improve help message for missing `self update` invocations ([#&#8203;8337](astral-sh/uv#8337))
-   Log `.netrc` parsing errors ([#&#8203;8364](astral-sh/uv#8364))
-   Remove trailing newlines in error messages ([#&#8203;8322](astral-sh/uv#8322))
-   Use a dedicated message for incompatible Python versions in wheel ABI tags ([#&#8203;8363](astral-sh/uv#8363))
-   Remove commands available in the top-level from the suggested subcommand error ([#&#8203;8316](astral-sh/uv#8316))

##### Release

-   Run release builds for `macos-x86_64` on `macos-14` runners ([#&#8203;8327](astral-sh/uv#8327))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@charliermarsh charliermarsh

Labels
compatibility Compatibility with a specification or another tool enhancement New feature or improvement to existing functionality
Projects
None yet
Milestone
v0.5.0
Development

Successfully merging this pull request may close these issues.
4 participants
@ericmarkmartin @charliermarsh @BurntSushi @pradyunsg