Wheel contains no dependency metadata when built via sdist
See original GitHub issueWhen I run python -m build
on our project, the resulting wheel doesn’t contain any dependency metadata.
When I run python -m build --sdist --wheel
it does.
Not sure if this is to do with using dynamic dependencies from a requirements.txt file or not.
build version 0.9.0 The project in question, for reference.
Issue Analytics
- State:
- Created a year ago
- Comments:20 (15 by maintainers)
Top Results From Across the Web
`poetry build` does not include locked transitive dependencies ...
Issue. When generating a pip-installable package using poetry build , the resulting packages's metadata does not include all of the locked ...
Read more >Sdists (again): Metadata standardisation incremental update
Wheel metadata are generated from the original user declaration in either setup.py , setup.cfg or pyproject.toml . IOW they are both treating ...
Read more >Build a wheel/egg and all dependencies for a python project
This will create a wheel file for your package. This assumes you don't have C/C++ headers, DLLs, etc. If you do, then you'll...
Read more >What Are Python Wheels and Why Should You Care?
In this tutorial, you'll learn what Python wheels are and why you should care as both a developer and end user of Python...
Read more >Knowledge Bits — Common Python Packaging Mistakes
There exists a PKG-INFO file containing the project metadata. For historical reasons, this does not include project dependencies.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think we established this was a build success, it caught a broken SDist mistake. 😃
I’m not sure a single package on PyPI does this (though I’ve seen a proposal for the manylinux one), certainly it’s not a problem in practice. But I do think this is why pip-tools and PDM have a harder time handling this.