As a Nixpkgs Python maintainer I often ask projects to include their tests in the sdist so we can run them when packaging. I prefer it also when an sdist basically represents a snapshot of a repository.

On Mon, Sep 10, 2018 at 8:08 AM, Thomas Kluyver <thomas@kluyver.me.uk> wrote:

On Mon, Sep 10, 2018, at 12:33 AM, Bert JW Regeer wrote:

Speaking as a maintainer of various different packages for the Pylons project, we include the following in our sdists:

- source code for the package

- tests for the package

- documentation for the package

and of course the license/history/changelog/everything you'd theoretically need to create a fork (minus .git). Our sdists are pretty big as a result.

When I was working out how Flit could build sdists without a MANIFEST.in, I settled on the idea that an sdist should be more or less a static equivalent of checking out the git tag for that release. So if a project lost its VCS history, all the files from release versions would still be in sdists. That means all the source files are there (like rst docs), but not generated files (like Sphinx HTML output).

Now that 'pip install' gets wheels where possible, there's less pressure to make sdists as slim as possible, because far fewer people will need to wait for them to download.

--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-leave@python.org
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/FOX6YWO2NPY6ONE4RDKVD5JCTWSTIDG3/

--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-leave@python.org
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/NRQ3JDCAJK5CLNGZQV3WXCCXE2EQE5V5/