-
Notifications
You must be signed in to change notification settings - Fork 679
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.
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
Error out when using the same normalised source twice #7229
Comments
Yeah, I think we should probably error in both cases. Good find. |
Agree though it's somewhat annoying to fix because these happen very far apart from one another. |
Yeah to be fair this is really just a tiny annoyance, mentioned it just because I stumbled across it 😄 |
It bothers me lol. |
When mapping dependencies to define sources, because of the TOML specification, uv will raise an error if defining the same source twice. For instance with this
pyproject.toml
:the following error will be raised:
(btw not sure we should have both a warning and error here)
But while uv applies normalisation for sources (similarly to dependencies), it will not error out if defining the same source twice with different casing that would result in the same name after normalisation:
Here, locking will work, and will end up choosing the latest source defined in the list (here in
python_multipart
, and if reversing the list,python-multipart
is chosen instead).Should uv also error out in this case, like it does when using the exact same casing?
The text was updated successfully, but these errors were encountered: