Re: Should an sdist/MANIFEST.in include docs and tests?
Ben Finney <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <[email protected]> |
Bert JW Regeer <[email protected]> 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 -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/OPIZIKGLQD3UVZQ2JK7M7YYVZN6JJ7VT/