Thomas Kluyver

Normally, everything which is checked into git should be included in the sdist made by `flit build`. That should include tests and docs (source files). Flit does not concern itself...

I'm not arguing with the need for tests or docs. But I don't see them as part of packaging. If you want to try to push standard ways for projects...

From my point of view, insisting that a packaging tool should have a way to build documentation is like saying that a toaster should be able to boil water -...

@mawillcockson do you think you'll get back to this, or would you like me to take it over?

The reasoning here is that Flit doesn't support any config options from the outside that would alter the metadata, so if you give it the same input files, you'll get...

That's actually more of a feature request :slightly_smiling_face: - there's currently no simple setting to disable the use of git/hg to determine what goes in the sdist. You would have...

I haven't entirely changed philosophy, but my view wasn't compatible with PEP 517's take on sdists, and I haven't resolved that. I focused on the thing you upload to PyPI,...

That's almost right, but in point 2 it should include license & readme files referenced in `pyproject.toml` (e.g. PEP 621 `project.license.file`), regardless of their extensions. There's no automatic inclusion based...

In general, if you want to ship a data file which the code uses, put it inside the package (with your Python code), and find it either with a relative...

No problem. I'll leave this open as a docs request, because it's only easy if you know about `__file__`.