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 David Carlier, Michael.Felt, barry, devnexen, koobs, ned.deily, pitrou, serhiy.storchaka, vstinner
Date 2018-05-24.15:00:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527174044.88.0.682650639539.issue32493@psf.upfronthosting.co.za>
In-reply-to
Content
Is AIX big-endian?

On *BSD systems uuid_t is a structure of integers with platform-depending endianess. Thus on little-endian platform UUID should be called with the bytes_le argument. This doesn't fix test on OpenBSD and NetBSD, but at least the result is stable (version=4).

Using bytes_le on Linux breaks tests. Seems uuid_generate_time_safe() always returns bytes in big-endian order.

PR 7098 adds _uuid.little_endian which is true on little-endian platforms using uuid_create(), and false otherwise. Actually there are many ways of solving this problem, the choice of this design was arbitrary. _uuid.generate_time_safe() could return a 3-tuple instead of 2-tuple, or there could be two separate functions: _uuid.generate_time_safe() and _uuid.create().
History
Date User Action Args
2018-05-24 15:00:44serhiy.storchakasetrecipients: + serhiy.storchaka, barry, pitrou, vstinner, ned.deily, koobs, Michael.Felt, David Carlier, devnexen
2018-05-24 15:00:44serhiy.storchakasetmessageid: <1527174044.88.0.682650639539.issue32493@psf.upfronthosting.co.za>
2018-05-24 15:00:44serhiy.storchakalinkissue32493 messages
2018-05-24 15:00:44serhiy.storchakacreate