The SRC_URI in pycparser-2.09.1 leads to bitbucket.org, but unfortunately this package is different from the one provided on PyPI. Some .py files are generated and included in the PyPI package, they are not included in bitbucket (only the sources from the repository are included). While these missing files are not really mandatory at first sight, they indeed are: if they are not included, .py files are generated in current path if you launch a script that uses pycparser. This behaviour has been reported here: https://bitbucket.org/eliben/pycparser/issue/3/ This issue has been fixed between 2.09 and 2.09.1: the tarball on PyPI has been changed to include the generated files. By the way, using bitbucket instead of PyPI is also possible, but you have to run _build_tables.py in the ebuild to generate the missing .py files. As the older tarballs are not stored on PyPI, it may be a better solution. Reproducible: Always
08 May 2013; Mike Gilbert <floppym@gentoo.org> +pycparser-2.09.1-r1.ebuild, -pycparser-2.09.1.ebuild: Pregenerate lexer and parser tables.
