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 vstinner
Recipients steve.dower, vstinner
Date 2020-05-04.16:42:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588610574.96.0.75136672364.issue40501@roundup.psfhosted.org>
In-reply-to
Content
uuid.py has a long history. The recent history is the addition of the _uuid module which exposes libuuid function properly. IMHO it's a better approach than ctypes.

On Windows, it seems like ctypes remains used to get access to Windows function UuidCreateSequential(). It is used by uuid.getnode() for example. We should expose UuidCreateSequential() in _uuid rather than using ctypes for that.

I propose to do that in two steps:

(A) Ensure that _uuid works on macOS, FreeBSD and Linux, especially in the macOS installer of python.org. If yes, remove the ctypes code to access libuuid functions.

(B) Add a function to _uuid to expose Windows UuidCreateSequential(), use it in uuid.py and remove the related ctypes code.

Both steps can be done in parallel.
History
Date User Action Args
2020-05-04 16:42:54vstinnersetrecipients: + vstinner, steve.dower
2020-05-04 16:42:54vstinnersetmessageid: <1588610574.96.0.75136672364.issue40501@roundup.psfhosted.org>
2020-05-04 16:42:54vstinnerlinkissue40501 messages
2020-05-04 16:42:54vstinnercreate