Closed njsmith closed 6 years ago
Resolved the first issue by doing git push --tags origin
. Apparently I forgot to do this after the last release, whoops.
.gitignore
issue, which I can't replicate? I'll email him back about that.Sounds like the .gitignore
issue is that they were looking at the snapshots that Github generates on the "releases" page. I think we could override this by uploading our release artifacts to Github, but that's an extra step on every release and mostly pointless, since PyPI is the archive of record, so not going to do anything about that for now.
In private email, Nicolas Boulenguez reported the following issues they encountered while working on packaging async_generator for Debian:
[x] The 1.9 tag is missing from Github.
[x] The source says that the license is "MIT or APACHE2 (your choice)" but the 1.9 tarball on pypi only mentions MIT.
[x] The 1.9 tarball on pypi contains no manual, neither the source nor the formatted version.
[ ]
If this is easy for you to do, please consider removing stuff specific to github like .gitignore from the release tarball. People like me downloading the tarball instead of cloning the repository might have a different workflow with their own .gitignore settings. If removing files from the tarball is convoluted with github, forget this suggestion. This is only a matter of convenience.