Are the .pyc / .pyo files safely architecture independent?
(I.e. are they now, and are they likely or even guaranteed
to remain so?).
I know the bytecode can change between interpreter
versions and other interpreters like Jython, Stackless, and
PyPy (does that exist yet?) may not even choose to
make them. But given that the same interpreter is made
available, will they work on, say, an ARM processor,
a 68K, and a i386 sharing them on the same network?
Thanks for any comments,
Terry
--
Terry Hancock
Anansi Spaceworks http://www.AnansiSpaceworks.com/
Yes.
Skip
> This question was brought up by packagers trying to set
> policy for including Python modules in Debian Gnu/Linux:
>
> Are the .pyc / .pyo files safely architecture independent?
> (I.e. are they now, and are they likely or even guaranteed
> to remain so?).
Yes. .pycs are marshalled code objects (mostly) so the notes in
http://www.python.org/doc/current/lib/module-marshal.html
apply.
Cheers,
mwh
--
CLiki pages can be edited by anybody at any time. Imagine the most
fearsomely comprehensive legal disclaimer you have ever seen, and
double it -- http://ww.telent.net/cliki/index
Yes. I don't know about future guarantees, but you may be assured that
it would be a Big Change if that were no longer true.
>I know the bytecode can change between interpreter versions and other
>interpreters like Jython, Stackless, and PyPy (does that exist yet?)
>may not even choose to make them. But given that the same interpreter
>is made available, will they work on, say, an ARM processor, a 68K, and
>a i386 sharing them on the same network?
Yes.
--
Aahz (aa...@pythoncraft.com) <*> http://www.pythoncraft.com/
Weinberg's Second Law: If builders built buildings the way programmers wrote
programs, then the first woodpecker that came along would destroy civilization.