Closed warsaw closed 9 years ago
Would a 4.1.1 release without those be helpful?
(Ha ha I can't do releases of 'persistent' anyway, only @jimfulton and @tseaver can.)
(Shameless plug: using check-manifest prevents this kind of mistake. It also integrates with zest.releaser seamlessly, if pip installed.)
On Jun 02, 2015, at 12:12 AM, Marius Gedminas wrote:
Would a 4.1.1 release without those be helpful?
Yes, please!
The persistent-4.1.0.tar.gz file on PyPI appears to contain
__pycache__/*.o
files from cffi. This is problematic for downstream consumers because the binary files don't correspond directly to source files. For example, this violates Debian policy, so the upstream tarball must be repacked to be made compliant with policy.I'm guessing this is just an artifact of the release process rather than something you actually want to do.