RetroSearch Browse

Sun Aug 3 00:46:42 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-August/081651.html

I was running the test suite and I noticed test_uuid's warning message
is still up:

test_uuid
    WARNING: uuid.getnode is unreliable on many platforms.
        It is disabled until the code and/or test can be fixed properly.
    WARNING: uuid._ifconfig_getnode is unreliable on many platforms.
        It is disabled until the code and/or test can be fixed properly.
    WARNING: uuid._unixdll_getnode is unreliable on many platforms.
        It is disabled until the code and/or test can be fixed properly.

The state of uuid has been like this for a while now. Are we going to
actively try to fix this, or was uuid a mistake? I guess my real
question is how long are we willing to let the code sit in this
partial state before we decide the module just is not getting enough
attention?

-Brett

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-August/081651.html below:

[Python-Dev] What to do with uuid?