Now that it is visible - maybe OpenBSD will treat it as a bug and get 
the "version bits" to work as their man page 
(https://man.openbsd.org/uuid.3) says it does:

  STANDARDS <https://man.openbsd.org/uuid.3#STANDARDS>

The *uuid_compare*(), *uuid_create*(), *uuid_create_nil*(), 
*uuid_equal*(), *uuid_from_string*(), *uuid_hash*(), *uuid_is_nil*(), 
and *uuid_to_string*() functions are compatible with the DCE 1.1 RPC 
specification.

The FreeBSD man page 
(https://www.freebsd.org/cgi/man.cgi?query=uuid_create) says:

*NAME* <https://www.freebsd.org/cgi/man.cgi?query=uuid_create#end>
      *uuid*_*compare*,*uuid*_*create*,	*uuid*_*create*_*nil*,*uuid*_*equal*,*uuid*_*from*_*string*,
      *uuid*_*hash*,	*uuid*_*is*_*nil*,*uuid*_*to*_*string*  -- DCE 1.1 compliant UUID func-
      tions

Re the DCE 1.1 RPC implementation/description - I found this link:
http://pubs.opengroup.org/onlinepubs/9629399/apdxa.htm

And this comment:

The version number is multiplexed in the 4 most significant bits of the 
*time_hi_and_version* field. UUID version Field 
<http://pubs.opengroup.org/onlinepubs/9629399/apdxa.htm#tagtcjh_35> 
lists currently defined versions of the UUID.

*msb1* 	*msb2* 	*msb3* 	*msb4* 	*Version* 	*Description*
0 	0 	0 	1 	1 	DCE version, as specified herein.
0 	0 	1 	0 	2 	DCE Security version, with embedded POSIX UIDs.

So, maybe either, or both: OpenBSD and FreeBSD fix their implementation. 
Problem solved?!

On 1/23/2018 3:34 PM, David CARLIER wrote:
> David CARLIER <devnexen@gmail.com> added the comment:
>
> In OpenBSD it s even "worse", the version for each call is random (not a surprise when looking at the source). The question is, do we go back to support only AIX or do we accept somehow wrong version ?
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue32493>
> _______________________________________
>