publishing-python-packages
pigar
| publishing-python-packages | pigar | |
|---|---|---|
| 2 | 1 | |
| 76 | 1,580 | |
| - | - | |
| 0.0 | 7.0 | |
| 25 days ago | 22 days ago | |
| Python | Python | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
publishing-python-packages
-
How to improve Python packaging, or why 14 tools are at least 12 too many
I don't agree with all the points from the article, but I do agree there is a depth of learning to be had about creating packages (and doing it repeatably/scalably). I wrote a book about creating Python packages that just came out: https://pypackages.com
Even this book doesn't cover all options in each area, and it skips almost wholly over conda because I have no personal experience using it. conda and the work in the scientific community adds complexity both to the creation and the consumption side of packaging, and that's one area I'm not sure this post covers all the nuance of when considering how a "one size fits all" solution might work in practice.
-
Publishing Python Packages: available now!
If reading code is more your thing, you might want to check out the code companion.
pigar
-
How to improve Python packaging, or why 14 tools are at least 12 too many
I am the author of pigar[1], and I am using Go a lot, Go has its problems too, but I am a fan of `import "url"` style import statement, developers can write code first, and sync the dependency later with `go mod tidy`.
To fix problems in Python's world, Python's community should simplify the tools and cultivate a habit to declare the dependency first(maybe this should be mandatory) and use it later.
[1]: https://github.com/damnever/pigar
What are some alternatives?
sigstore-python - A Sigstore client for Python
req2toml - Convert requirements.txt to poetry toml 🚀
pythonfluente2e - Python Fluente, Segunda Edição
roadmap - Public roadmap for the Poetry package manager
pip-upgrade - Upgrade your pip packages with one line. A fast, reliable and easy tool for upgrading all of your packages while not breaking any dependencies
tox-pin-deps - Run tox environments with strictly pinned dependencies (and no project or code changes).
pip-audit - Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them
pragmatic-debian-packages - Pragmatic Debian packaging