Closed polyzen closed 2 years ago
Perhaps yes, the tar-ball should include the tests. Although I would want to enhance the GitHub Actions to actually test this, and I lean to a more explicit manifest over grafting (to avoid accidental inclusion of files on the developer's working repository).
What I normally do is build the wheel and tar-ball, locally install the wheel, unzip the tarball, cd into the decompressed tarball, and run the tests there. This catches an incomplete manifest.
So what should be done here?
I'm not sure what building a tarball entails here.
The command python setup.py sdist --formats=gztar
makes a Python source distribution tar-ball.
What I wanted was to replicate my release process (and test it), which is currently documented here:
The 0.3.2 release on PyPI does not have the commas and black_preview files added since the 0.2.4 release. Perhaps this is needed?