summaryrefslogtreecommitdiffstats
path: root/Mac
diff options
context:
space:
mode:
authorSjoerd Mullender <sjoerd@acm.org>2004-01-10 20:43:43 (GMT)
committerSjoerd Mullender <sjoerd@acm.org>2004-01-10 20:43:43 (GMT)
commit7e6bbe15162b7307174645e9c4eb2809931b1800 (patch)
treeea1875e446bad683581ee95c3ac11c81befcb2eb /Mac
parent2e5e6445e7ab0c025061b13462cccf9321a4fa3e (diff)
downloadcpython-7e6bbe15162b7307174645e9c4eb2809931b1800.zip
cpython-7e6bbe15162b7307174645e9c4eb2809931b1800.tar.gz
cpython-7e6bbe15162b7307174645e9c4eb2809931b1800.tar.bz2
The format of the string data used in the imageop module is described
as "This is the same format as used by gl.lrectwrite() and the imgfile module." This implies a certain byte order in multi-byte pixel formats. However, the code was originally written on an SGI (big-endian) and *uses* the fact that bytes are stored in a particular order in ints. This means that the code uses and produces different byte order on little-endian systems. This fix adds a module-level flag "backward_compatible" (default not set, and if not set, behaves as if set to 1--i.e. backward compatible) that can be used on a little-endian system to use the same byte order as the SGI. Using this flag it is then possible to prepare SGI-compatible images on a little-endian system. This patch is the result of a (small) discussion on python-dev and was submitted to SourceForge as patch #874358.
Diffstat (limited to 'Mac')
0 files changed, 0 insertions, 0 deletions