Complain more loudly about unknown Dependency Object Specifiers

[Gankra]

Summary

This currently does not produce an error or default-visible warning. (It results in a tracing::warn! which is hidden by default):

[dependency-groups]
foo = ["pyparsing"]
bar = [{set-phasers-to = "stun"}]

The set-phasers-to get parsed as an unknown Dependency Object Specifier (DependencyGroupSpecifier::Object), which is a future-compat concept from PEP-735 dependency-groups:

Tools SHOULD error when evaluating or processing unrecognized data in Dependency Groups.

Tools SHOULD NOT eagerly validate the list contents of all Dependency Groups.

This means that in the presence of the (above example), most tools will allow the foo group to be used, and will only error when the bar group is used.

"When the group is used" is a fuzzy concept because we generate lockfiles that are supposed to validate/cover all possible invocations. As such we should probably error when we encounter these, or at least unconditionally warn to stderr!

Platform

all

Version

uv 0.6.11

Python version

No response

[kiran-4444]

I'd love to work on this.

[zanieb]

Feel free to put up a pull request.

[kiran-4444]

Thanks! Can you assign this to me so that I won't lose track of it?

[kiran-4444]

Umm, how do I reproduce this locally using cargo run from the uv clone directory? Do I have to create a new workspace with a pyproject.toml in it?

Sorry if this seems too basic, this is my first time working with this locally (but I have used uv, though, mostly as pip replacement

[zanieb]

I would uv init example && cd example, then edit pyproject.toml, then cargo run -- uv sync or similar.