This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Rudd-O
Recipients Rudd-O, tarek
Date 2009-03-14.08:45:24
SpamBayes Score 2.8352199e-08
Marked as misclassified No
Message-id <1237020326.68.0.587909331864.issue5482@psf.upfronthosting.co.za>
In-reply-to
Content
More info:

From my wicked noarch RPM compiled in an i386 machine, installed into my
64 bit centos (same OS):

[rudd-o@tobey ~]$ python
Python 2.4.5 (#1, Mar 13 2009, 12:13:36)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import wicked
>>> wicked.__file__
'/usr/lib/site-python/wicked/__init__.pyc'

Evidence that the compiled file is being not recompiled, and is being
used directly on import, even across architectures.

-------------

However, I have discovered that I cannot run the same pyc file across
interpreters, even though the py file would run, so I am stumped at
this.  The reason i am stumped is that I can find a
platform-independent, interpreter-independent dir (site-python), and a
platform-dependent, interpreter-dependent dir (site-packages), but NOT a
platform-independent, interpreter-dependent dir, which is the BIG issue
here if we want to at least avoid having to rebuild python packages for
different architectures with the SAME interpreter.

Ideas?  I am thirsty for more knowledge here and losing hope.
History
Date User Action Args
2009-03-14 08:45:26Rudd-Osetrecipients: + Rudd-O, tarek
2009-03-14 08:45:26Rudd-Osetmessageid: <1237020326.68.0.587909331864.issue5482@psf.upfronthosting.co.za>
2009-03-14 08:45:25Rudd-Olinkissue5482 messages
2009-03-14 08:45:24Rudd-Ocreate