publishing-python-packages
roadmap
| publishing-python-packages | roadmap | |
|---|---|---|
| 2 | 4 | |
| 76 | 2 | |
| - | - | |
| 0.0 | 1.8 | |
| about 1 month ago | over 2 years ago | |
| Python | ||
| 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.
roadmap
-
Python Packaging, One Year Later: A Look Back at 2023 in Python Packaging
I wish Poetry were PEP-621 compliant though. [1]
Currently, it uses a proprietary configuration group (or "tool section", as they seem to call it in `pyproject.toml` speech).
[1]: https://github.com/python-poetry/roadmap/issues/3
-
How to improve Python packaging, or why 14 tools are at least 12 too many
https://github.com/python-poetry/roadmap/issues/3
-
What are people using to organize virtual environments these days?
Sorry for the late reply. I cannot recall the exact source, but I found this issue in the poetry repo: https://github.com/python-poetry/roadmap/issues/3. IIUC, they are trying to make poetry compliant with PEP621 but the PR was not merged yet? Will update the original comment to add this nuance.
-
How to create a Python package in 2022
I believe that Poetry does conform to PEP 518 (i.e. it specifies `[build-system]requires`), but not to the `dependencies` part of PEP 621 [1]. There are plans for this in the future though [2].
[1] https://peps.python.org/pep-0621/
[2] https://github.com/python-poetry/roadmap/issues/3
What are some alternatives?
sigstore-python - A Sigstore client for Python
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
pigar - :coffee: A tool to generate requirements.txt for Python project, and more than that. (IT IS NOT A PACKAGE MANAGEMENT TOOL)
pythonfluente2e - Python Fluente, Segunda Edição
Nuitka - Nuitka is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11. You feed it your Python app, it does a lot of clever things, and spits out an executable or extension module.
tox-pin-deps - Run tox environments with strictly pinned dependencies (and no project or code changes).