publishing-python-packages
tox-pin-deps
| publishing-python-packages | tox-pin-deps | |
|---|---|---|
| 2 | 1 | |
| 76 | 3 | |
| - | - | |
| 0.0 | 10.0 | |
| 25 days ago | about 1 year ago | |
| Python | Python | |
| MIT License | MIT 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.
tox-pin-deps
-
I moved away from Poetry for Python
I recently developed a tox plug-in, tox-pin-deps [1], that integrates the pip-compile workflow with dependencies specified in tox.ini (per environment). This was in response to both poetry and Pipenv being non-standard and consistent stumbling blocks for ramping up new devs on the team.
Despite the shiny, I seem to always find my way back to standard tools and text files.
[1]: https://github.com/masenf/tox-pin-deps
What are some alternatives?
sigstore-python - A Sigstore client for Python
zpy - Zsh helpers for Python venvs, with uv or pip-tools
pigar - :coffee: A tool to generate requirements.txt for Python project, and more than that. (IT IS NOT A PACKAGE MANAGEMENT TOOL)
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
pythonfluente2e - Python Fluente, Segunda Edição
frelatage - Coverage-based fuzzer for python applications
roadmap - Public roadmap for the Poetry package manager
locust - Write scalable load tests in plain Python 🚗💨
create-tox-app - CLI tool similar to create-react-app that creates basic env with tox.
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
dephell - :package: :fire: Python project management. Manage packages: convert between formats, lock, install, resolve, isolate, test, build graph, show outdated, audit. Manage venvs, build package, bump version.
manticore - Symbolic execution tool