On 03/12/2017 11:34 AM, Ghislain Vaillant wrote:
> On the other hand, I have seen very few pieces of software which had a
> *comprehensive* MANIFEST.in for generating a tarball suitable for
> packaging. The file is often either absent, or missing inclusion of the
> docs, tests, change log or license files. Upstream is usually receptive
> in providing "better" source tarballs, but I have had some developers
> taking an aggressive stance towards keeping the PyPI tarball as minimal
> as possible in the past.

IMO, upstream are right that the PyPi releases should be minimal. They
are, from my view point, a binary release, not a source release.

It makes a lot of sense to therefore use the git repository, which is
what I've been doing as much as possible.


Thomas Goirand (zigo)

Reply via email to