Bug#953992: ITP: python-flit -- simple way to put Python packages and modules on PyPI
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman <debian@kitterman.com>
* Package name : flit
Version : 2.2.0
Upstream Author : Thomas Kluyver <thomas@kluyver.me.uk>
* URL : https://github.com/takluyver/flit
* License : BSD 3-clause license
Programming Lang: Python
Description : simple way to put Python packages and modules on PyPI
Flit is a simple way to put Python packages and modules on PyPI. It tries to
require less thought about packaging and help you avoid common mistakes.
.
Flit supports PEP 517 Python packaging.
.
Make the easy things easy and the hard things possible is an old motto from
the Perl community. Flit is entirely focused on the easy things part of that,
and leaves the hard things up to other tools.
.
Specifically, the easy things are pure Python packages with no build steps
(neither compiling C code, nor bundling Javascript, etc.). The vast majority
of packages on PyPI are like this: plain Python code, with maybe some static
data files like icons included.
I intend to maintain this in PAPT (Python Applications Packaging Team).
PEP 517 style packages are becoming more common and while flit does
generate a setup.py file for non-PEP 517 build system use, it is not
particularly satisfying. I'm motivated to package this after having had
to patch such a package to make it build complete metadata. Debian will
be better off if we can use the upstream tools.
Upstream provides a good discussion of why flit in addition to other
Python oriented build tools:
https://flit.readthedocs.io/en/latest/rationale.html
Flit does use flit to build, but it includes a bootstrap script so it
can build itself without in archive bootstrapping.
Reply to: