Description of problem:
Python 3.2 moves where Python bytecode (.pyc/.pyo) goes relative to the .py file; this was PEP 3147:
This leads to false warnings from rpmlint on Python 3.2 extension modules; see e.g.:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpmlint on a Python 3.2 module (e.g. the one from but 634700)
W: python-bytecode-without-source /usr/lib64/python3.2/site-packages/FOO/__pycache__/__init__.cpython-32.pyo
W: python-bytecode-without-source /usr/lib64/python3.2/site-packages/FOO/__pycache__/__init__.cpython-32.pyc
The above files are correct; there should be no warning
Created attachment 450045 [details]
Initial attempt at fixing this
This suppresses the false positive (patch against 0.99 tarball)
Created attachment 450046 [details]
Better version of the patch
Thanks. The patch broke non-PEP-3147 source lookup (always returned None even if the source was found), fixed version applied upstream:
rpmlint-1.0-1.fc14 has been submitted as an update for Fedora 14.
rpmlint-1.0-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update rpmlint'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/rpmlint-1.0-1.fc14
rpmlint-1.0-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.