[Laszlo (Laca) Peter]
> I work in the team that delivers python on Solaris. Recently we've
> been getting requests for delivering python in 64-bit as well
> as in 32-bit. As you probably know, Solaris can run 64-bit and
> 32-bit binaries on the same system, but of course you can't mix and
> match shared objects with different ISAs. This seems to apply to
> python bytecode as well: the pyc files generated by a 64-bit build
> of python are incompatible with those generated by the 32-bit python.
> Note the caveat at
> http://aspn.activestate.com/ASPN/docs/ActivePython/2.3/python/lib/module-marshal.html
Which caveat, specifically? As it says there, the only known problem
was fixed in Python 2.2:
This behavior is new in Python 2.2. In earlier versions, all but the least-
significant 32 bits of the value were lost, and a warning message
was printed
> I guess my first question is if there are any plans to make the
> bytecodes for different ISAs compatible. That would make most of
> our problems magically go away (;
I suspect they already have ;-) There are no plans to make marshal
store a Python long object on a 64-bit box for integers that fit in 64
points but not in 32 bits, and there would be very little point to
doing so. As the referenced page says, you get the same numeric value
regardless. It's /possible/ to write Python code to detect the
difference in type, but real code wouldn't do that.
> ...
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
