Open maxime1907 opened 2 weeks ago
This is an edge case; we probably need to add some logic to drop the origin requirements if they are recursive extras, as they are redundant if the dependencies they imply are already part of the requirements file. That should happen directly after the resolution process. It's rather low priority, I presume, we have a lot of other issues to tackle right now - you're welcome to try and draft a fix, of course.
When pyproject.toml references its own local package to recursively include extra dependencies, it outputs a requirements.txt file which references the local package with the absolute path which is a problem as its not portable and should instead just list the dependencies
It was previously possible with setup.py with this configuration:
Environment Versions
Steps to replicate
[build-system] requires = ["setuptools>=69.1", ] build-backend = "setuptools.build_meta"
[project.optional-dependencies] dev = ["package[test,tools]"] tools = ["build"] test = ["pyyaml"]
Expected result
Actual result
Linked issues