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

[Justus Winter]

Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:

> [ Unknown signature status ]
> On Thu 2016-09-22 04:55:38 -0400, Justus Winter wrote:
>> Daniel Kahn Gillmor <dkg at fifthhorseman.net> 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- https://gnupg.org/ftp/gcrypt/gpgme/gpgme-1.7.1.tar.bz2 | tar tj | grep pyc
> gpgme-1.7.1/lang/python/pyme/__pycache__/
> gpgme-1.7.1/lang/python/pyme/__pycache__/version.cpython-34.pyc
> gpgme-1.7.1/lang/python/pyme/__pycache__/__init__.cpython-34.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 :)

I tried to reproduce this again, and failed again.  This must be
specific to how Werner builds the distribution tarballs.

% tar tf gpgme-1.7.1-beta47.tar.bz2|grep pyc|wc --lines
0

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