self-contained-runnable-py
emacs-python-exec-find
Our great sponsors
| self-contained-runnable-py | emacs-python-exec-find | |
|---|---|---|
| 3 | 1 | |
| - | 5 | |
| - | - | |
| - | 10.0 | |
| - | over 1 year 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.
self-contained-runnable-py
-
Underappreciated Challenges with Python Packaging
The approach I prefer is to not mess with setuptools etc at all in the first place, and simply make a nice executable package.
e.g. https://github.com/tpapastylianou/self-contained-runnable-py...
-
How to create a Python package in 2022
The title should be: How to create a "Python DISTRIBUTION package".
The term "python package" means something entirely different (or at the very least is ambiguous in a pypi/distribution context).
To add to the confusion, creating a totally normal, runnable python package in a manner that makes it completely self-contained such that it can be "distributed" in a standalone manner, while still being a totally normal boring python package, is also totally possible (if not preferred, in my view).
Shameless plug: https://github.com/tpapastylianou/self-contained-runnable-py...
-
Show HN: Hatch 1.0.0 – Modern, extensible Python project management
Shameless plug: I use my own template, which organises things as runnable projects.
https://github.com/tpapastylianou/self-contained-runnable-py...
It serves my purposes very well (which is creating projects that represent standalone experiments).
Sharing in case someone else here finds it useful.
More recently I've modified this a bit to also generate nice html reports straight from the __main__.py file, independently of the underlying python code, and use this as lab books (where each lab book contains a single analysis and its report). I'll upload this template separately when I find the time.
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
What are some alternatives?
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
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
pip-tools - A set of tools to keep your pinned Python dependencies fresh.
hatch - Modern, extensible Python project management
release-please - generate release PRs based on the conventionalcommits.org spec
pip-audit - Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them
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
Poetry - Python packaging and dependency management made easy
warehouse - The Python Package Index