Include all the source files in MANIFEST.in

Because otherwise doc/INSTALL.rst lies to users when it tells them the source tarball will have a buildout.cfg and everything. Lying to users is Bad. (I don't know what to do about the .mo files that are in git. Should they be included in the sdist?)

Include all the source files in MANIFEST.in
Because otherwise doc/INSTALL.rst lies to users when it tells them the source tarball will have a buildout.cfg and everything. Lying to users is Bad. (I don't know what to do about the .mo files that are in git. Should they be included in the sdist?)
d08c2737 · Marius Gedminas · 7f9616d1 · d08c2737
Commit d08c2737 authored Apr 02, 2014 by Marius Gedminas
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 0 deletions

MANIFEST.in MANIFEST.in +6 -0

No files found.
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -7,3 +7,9 @@ global-exclude *.dll
 global-exclude *.pyc
 global-exclude *.pyo
 global-exclude *.so
+
+include *.py
+include .travis.yml
+include buildout.cfg
+include sources.cfg
+include versions.cfg