Soren Stoutner <so...@debian.org> writes: >> - This uses tarballs from pypi.debian.net, which isn't identical to >> upstream's GitHub git archive. It seems tests/ are missing. I've >> approached upstream about including them in the PyPI upload -- >> https://github.com/vmagamedov/grpclib/issues/200 -- but I'm not sure >> what the best practices are here. Is using the pypi.debian.net >> tarball recommended? Or do people package the github.com tarball >> instead? Or directly from git? What do we do when some stuff is >> missing from the PyPI archive? > > I am not experienced enough with Python packaging to respond to your other > questions, but I do know that many Python packages pull from github or gitlab > when thinks like tests are missing from PyPI, so you should feel free to do > so > when needed.
Thanks for insight! This is good to know. I prefer to ask upstreams to include the relevant stuff into the PyPI tarball instead. However if it turns out upstreams don't want to do that (or that doing so is against PyPI best practices somehow) AND there is significant advantage in using upstream's github as the tarball source, then at least I know this isn't considered a big no-no for Debian packages. So far I've only noticed that some self-tests and auxilliary files are missing from the PyPI tarballs, and I don't consider that to be important enough to deviate from using the pypi.debian.net sources yet. /Simon
signature.asc
Description: PGP signature
