On Dec 21, 2012 2:53 AM, "Miroslav Suchý" <firstname.lastname@example.org> wrote:
> On 12/20/2012 01:43 AM, Garrett Holmstrom wrote:
>> There's also the fact that the ABI for the bytecode that gets generated
>> at build time is specific to each x.y series of python releases.
> Well it is even specific for each architecture and we do not mind to flag such packages as noarch. I mean that .pyc generated on i686 is different from x86_64 version.
> However I'm not sure how much those two are compatible.
This is incorrect. Python bytecode is arch independent. The .pyc files from one compilation are different from a second compilation out its true. But this is because a timestamp is embedded in the bytecode cache files (.pyc) so that python can tell whether a .pyc or a .py should be used when it finds both on disk.
> Miroslav Suchy
> Red Hat Systems Management Engineering
> packaging mailing list