emacs-python-exec-find
roadmap
| emacs-python-exec-find | roadmap | |
|---|---|---|
| 1 | 4 | |
| 5 | 2 | |
| - | - | |
| 10.0 | 1.8 | |
| over 1 year ago | over 2 years ago | |
| Emacs Lisp | ||
| GNU General Public License v3.0 only | - |
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.
emacs-python-exec-find
-
How to create a Python package in 2022
I initially had some problems, then I've written an emacs package[1] to fix all of them. And it's due to the course of writing this package made me realize just how bad pre-commit is from its UX, design to its entire premise.
[1]: https://github.com/wyuenho/emacs-python-exec-find
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?
emacs-pet - Tracks down the correct Python tooling executables from your virtualenvs so you can glue the binaries to Emacs and delete code in init.el
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
sigstore-python - A Sigstore client for Python
release-please - generate release PRs based on the conventionalcommits.org spec
publishing-python-packages - Examples and exercises for Publishing Python Packages from Manning Books 🐍 📦 ⬆️
awesome-devops - A curated list of awesome DevOps platforms, tools, practices and resources
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.
Google Fonts - Font files available from Google Fonts, and a public issue tracker for all things Google Fonts
pigar - :coffee: A tool to generate requirements.txt for Python project, and more than that. (IT IS NOT A PACKAGE MANAGEMENT TOOL)
Poetry - Python packaging and dependency management made easy
warehouse - The Python Package Index