I strongly agree with this. I think a lot of the consumers of sdists are people packaging projects for distributions (fedora, debian, arch, etc), and they want to run the tests for their package.
I don't install tests for various reasons, including the fact that they are not part of the public interface of the package.
On September 10, 2018 1:17:45 AM UTC, Ben Finney
Bert JW Regeer
writes: 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.
In our wheels we ship:
- source code for the package/software
And nothing else, tests are not included in the wheel.
That seems like an eminently sensible scheme: The ‘wheel’ is for installation and should be targeted only to that; the ‘sdist’ is the source distribution and should contain all the source.
-- \ “You can stand tall without standing on someone. You can be a | `\ victor without having victims.” —Harriet Woods, 1927–2007 | _o__) | Ben Finney -- 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/O...