[issue3581] failures in test_uuid

[Stefan Krah]

Stefan Krah <stefan-usenet at bytereef.org> added the comment:

Sorry, the random node id generation in uuid.py is correct. The least
significant bit of the first octet (which is set to 1) is the first
one transmitted on the network, then the "low 47 random bits" follow.

I assumed that the least significant bit of the first octet was part
of the low 47 bits.



Patch test_uuid3 addresses points 1-5 and is almost the same as
test_uuid.patch, so I reset the resolution to 'accepted'.

As I said, there isn't much left that check_node() can check. One
could possibly check that a MAC address retrieved by ifconfig does
not have the multicast bit set, but what if a user has set the
hardware MAC to a strange value? Correctly retrieving that value
can't be regarded as a failure of uuid.py.


Should the patch go into the maintenance branches as well (after the
beta is out)?

----------
keywords: +patch -needs review
Added file: http://bugs.python.org/file16850/test_uuid3.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3581>
_______________________________________