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 Michael.Felt
Recipients Michael.Felt, pitrou
Date 2017-12-22.09:00:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513933224.15.0.213398074469.issue32399@psf.upfronthosting.co.za>
In-reply-to
Content
Understood.

What I have learned.

Although the types are quite different, they are both 16 bytes.

Starting with AIX 6.1, libc includes uuid_create(&uuid, &status)
which fills "uuid" with a uuid.uuid1() like result.
After calling uuid_to_string( &uuid, &uuid_string, &status); the result:
"13d866fa-e6f1-11e7-8017-fad18cf76204"

Further reading of the documentation within """ and """ in Lib/uuid.py helps me realize that the AIX approach aligns with the UUID fields description:

        fields      a tuple of the six integer fields of the UUID,
                    which are also available as six individual attributes
                    and two derived attributes:

            time_low                the first 32 bits of the UUID
            time_mid                the next 16 bits of the UUID
            time_hi_version         the next 16 bits of the UUID
            clock_seq_hi_variant    the next 8 bits of the UUID
            clock_seq_low           the next 8 bits of the UUID
            node                    the last 48 bits of the UUID


So - with this: there is also more than can be done for AIX re: https://bugs.python.org/issue28009

More to come...
History
Date User Action Args
2017-12-22 09:00:24Michael.Feltsetrecipients: + Michael.Felt, pitrou
2017-12-22 09:00:24Michael.Feltsetmessageid: <1513933224.15.0.213398074469.issue32399@psf.upfronthosting.co.za>
2017-12-22 09:00:24Michael.Feltlinkissue32399 messages
2017-12-22 09:00:23Michael.Feltcreate