byte-compiled python in gpgme download tarballs [was: Re: GnuPG Made Easy (GPGME) 1.7.0 released]

Daniel Kahn Gillmor dkg at
Mon Oct 24 21:34:16 CEST 2016

On Thu 2016-09-22 04:55:38 -0400, Justus Winter wrote:
> Daniel Kahn Gillmor <dkg at> writes:
>> I'm a curious about the inclusion of .pyc (byte-compiled python) in the
>> upstream tarball:
>> 0 dkg at alice:~$ tar tj < gpgme-1.7.0.tar.bz2  | grep pyc
>> gpgme-1.7.0/lang/python/pyme/__pycache__/
>> gpgme-1.7.0/lang/python/pyme/__pycache__/version.cpython-34.pyc
>> gpgme-1.7.0/lang/python/pyme/__pycache__/__init__.cpython-34.pyc
>> 0 dkg at alice:~$ 
>> Is this intentional, or an oversight?  If it's intentional, what do you
>> expect distributors to do with these files?
> That is not intentional, and strange, usually make distcheck is quite
> strict, isn't it?  Also, I just tried, and I cannot reproduce this.

Somehow, this has happened again in 1.7.1:

0 dkg at alice:~$ wget -q -O- | tar tj | grep pyc
0 dkg at alice:~$  

It's not the end of the world, it'd be nice to avoid this happening for
1.7.2 :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: </pipermail/attachments/20161024/af515031/attachment.sig>

More information about the Gnupg-devel mailing list