homepage

> I'm wondering if there may be a deeper problem here: how certain are we that bdist_rpm isn't using the system Python
> to handle the byte compilation step? It would explain why the files are still being generated in the old locations.
I’ve had a quick look at bdist_rpm and found nothing suspect (like filename + 'c'). You may have the right idea: There are --python and --fix-python options for this command that decide what executable will be used to run setup.py, so maybe the system Python is used. The default is 'python' instead of 'python3' though, so if that’s the cause I don’t understand how it worked at all.
> It occurs to me there's a way to check my theory: if we update the failing test to explicitly check the magic cookie in at
> least one of the precompiled pyc files (rather than just expecting the files' existence), then it should also start failing
> on the 2.7 RHEL 6 buildbot.
I’ve been looking for a way to inspect byte-compiled files for some time; please share any ideas on #13473.
To help debug this, I could apply #11599.
The rpm vs. rpmbuild bug is #11122.
#5875 and #13307 are bugs similar to this one.