➜

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 serhiy.storchaka
Recipients christian.heimes, pitrou, serhiy.storchaka
Date 2012-10-08.16:48:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
I agree, it is worth bring order to work with endianess. We can get rod of BYTEORDER_IS_BIG_ENDIAN and BYTEORDER_IS_LITTLE_ENDIAN in Objects/unicodeobject.c, IS_LITTLE_ENDIAN in Objects/longobject.c, tests in other modules. I don't see the necessity in new macros. WORDS_BIGENDIAN is enough.

If something failing on a big endian Solaris, build script should just define WORDS_BIGENDIAN.
History
Date User Action Args
2012-10-08 16:48:31serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, christian.heimes
2012-10-08 16:48:31serhiy.storchakasetmessageid: <[email protected]>
2012-10-08 16:48:31serhiy.storchakalinkissue16166 messages
2012-10-08 16:48:31serhiy.storchakacreate