Open soof-golan opened 3 weeks ago
We should fall back to building instead of trying to the read the metadata here, as we're doing in other cases, this is a bug.
Is there a reason you're using [project.urls]
here instead of [tool.poetry.urls]
?
@konstin Thanks for the fast response :) This is not a project I own / maintain, but an external package that is specified as a git dependency in another project.
(This is why I wrote seemingly valid)
uv fails to install a (seemingly) valid python dependency
@konstin -- I'm somewhat unsure... It is spec-incompliant. If we accept it here, we risk false negatives for other projects.
Oh right, because it's not dynamic like in the other cases.
We should change the error message with a note about the [project]
table spec, maybe linking to https://packaging.python.org/en/latest/guides/writing-pyproject-toml/
The toml crate doesn't give us this information unfortunately, so we can add better context to the error message: https://github.com/toml-rs/toml/issues/778
Hey Astral team!
I found an interesting behavior around installing a git based project that is managed by poetry (as opposed to any other build system). Since the name of the project is defined under the
tool.poetry
section uv fails to pick it up when reading the pyproject.toml file. I'm not sure if this is considered Poetry's fault, but pip definitely succeeds in installing this exact package. I have not checked whether this issue can be also replicated locally with a relative path package.Many thanks 🙏
What Happens
uv fails to install a (seemingly) valid python dependency. pip successfully installs this project.
Expected Behavior
uv should install the package
Reproduction
outputs:
uv --version
Platform
macOS Sonoma