[issue7650] test_uuid is invalid

Stefan Krah added the comment: Fixed in issue 3581. Thanks for the report and the comments! -- assignee: -> skrah dependencies: +failures in test_uuid keywords: +patch resolution: -> accepted stage: needs patch -> committed/rejected status: open -> closed superseder: -> failures in t

[issue7650] test_uuid is invalid

Austin English added the comment: >From Juan Lang, who originally pointed out the bug: My only comment is that the message is now misleading: -individual_group_bit = (node >> 40L) & 1 -universal_local_bit = (node >> 40L) & 2 message = "%012x doesn't look like a real MAC

[issue7650] test_uuid is invalid

Stefan Krah added the comment: The multicast bit is the least significant bit of the first octet. Could you check if the patch for http://bugs.python.org/issue3581 fixes your problem? -- nosy: +skrah ___ Python tracker

[issue7650] test_uuid is invalid

Changes by Brian Curtin : -- priority: -> normal stage: -> needs patch type: -> behavior versions: +Python 2.6, Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue7650] test_uuid is invalid

Austin English added the comment: More info from the wine bug: Whoops, I didn't notice that Python uses UuidCreateSequential. From MSDN: For security reasons, UuidCreate was modified so that it no longer uses a machine's MAC address to generate UUIDs. UuidCreateSequential was introduced to

[issue7650] test_uuid is invalid

New submission from Austin English : >From http://bugs.winehq.org/show_bug.cgi?id=21276 "I believe this is a bug in the python test code, not in Wine. Wine's UuidCreate function follows RFC 4122, section 4.4. That is, it generates a Uuid from a pseudorandom number generator, not from a MAC ad