flit
flit copied to clipboard
pypa
Simplified packaging of Python modules
I would like to specify default command line options for my project. flit would pick these up in addition to what is on the command line. for example, i might...
This builds a wheel and unzips it to `site-packages`, which is my suggestion for how downstream packagers bootstrap packaging tools. This isn't the only possible approach: https://github.com/FFY00/python-bootstrap shows how to...
Hi! PyPI's getting ready to add upload tokens to its API, so packagers can upload using tokens instead of username/password. I thought you might want to test and verify that...
This extends the CLI, and provides a command wrapper for an additional public function, `install_requirements()`. This will skip installing the user's code, but will still install all required dependencies. This...
In [the docs](https://flit.pypa.io/en/latest/pyproject_toml.html#sdist-section) it notes that building via a frontend other than `flit` includes a "minimal" set of files needed to build the sdist. Please could the docs be amended...
When flit_core is generating allowed files into sdist https://github.com/pypa/flit/blob/ec6e6b7c8994d5e79d0fd951d9e4c26a7c5d9977/flit_core/flit_core/sdist.py#L109-L118 it does not use https://github.com/pypa/flit/blob/ec6e6b7c8994d5e79d0fd951d9e4c26a7c5d9977/flit/sdist.py#L98-L101 for filtering on output files which results in Python bytecode ending up in package. Looks like...
Flit came about in a very different world, before various standards defined how packaging tools should work together (in particular, PEPs [517](https://www.python.org/dev/peps/pep-0517/), [621](https://www.python.org/dev/peps/pep-0621/) and [660](https://www.python.org/dev/peps/pep-0660/)). A lot of design decisions...
The setuptools world has a module `setuptools_scm` which allows setting the version directly from the SCM in use for the project. For example, if a commit is tagged with a...
Scenario: package heavily uses docker and needs building/rebuilding on every commit. Typical old way is to have requirements.txt that are passed to docker and installed first, then whole package is...
Could flit be made to output warnings when `flit.buildapi` backend is used? I think there's no reason to use it rather than `flit_core.buildapi`, is there?
