pypi tarball no longer includes documentation.py

[jelly]

The released tarball contains tests/test.py but lacks tests/documentation.py which makes it impossible to run the unit tests during an Arch Linux package build.

[micheles]

I decided to remove the tests from the tarball, I am not sure why test.py Is still there. I will have a look.

[micheles]

In the wheel test.py is missing, as I expected, but it is present in the tarball, seems to be an idiosyncrasy of the new build process (python -m build) which is ignoring the MANIFEST or something (building a Python package keeps getting more complicated).

[jelly]

Ok, I would still like to run the unit tests during the building of the Arch Linux package to confirm that newer Python versions work correctly. So as alternative I am happy to switch to using git sources but I noticed there is no tag for 5.2.0

[micheles]

Ah, I forgot to push the tag! It is there now: https://github.com/micheles/decorator/releases/tag/5.2.0

[mgorny]

I decided to remove the tests from the tarball, I am not sure why test.py Is still there.

That really sucks for us. Running the the test suite is crucial for packagers, as well as having a reliable source package available. And given that this is a pure Python package, all pip users use wheels anyway, so we're practically the only users of source packages.

[micheles]

I am willing to make changes to help you packagers. My thinking was that everybody use wheels and people wanting the sources can get them from github: https://github.com/micheles/decorator/archive/refs/tags/5.2.0.tar.gz.
Actually, in the future I would like to generate the PyPI package directly from an action in GitHub. If you have suggestions to offer or recipes to fix the current generation of the source package, please let me know.

[jelly]

For Arch I have switched to using Git as the source so if there are tags then it's all good.

[mgorny]

people wanting the sources can get them from github: https://github.com/micheles/decorator/archive/refs/tags/5.2.0.tar.gz.

Git archives are unfortunately unreliable. Besides, we'd rather see source distributions in top shape, since once release signing lands in PyPI, they'll be even more important.

Actually, in the future I would like to generate the PyPI package directly from an action in GitHub. If you have suggestions to offer or recipes to fix the current generation of the source package, please let me know.

I'll take a shot at fixing the build. As for GitHub Actions, I think literally the equivalent of:

python -m build
twine upload dist/*

would work here. However, I'm not experienced with that. GitHub workflows have been compromised too many times for me to trust them for making releases.