Michael Felt <mich...@felt.demon.nl> added the comment:
Considering that _uuid is now working for AIX issue32399 - I need to get some
things straight (aka some help please).
Does uuid.py (./Lib/uuid.py) call _uuid.py?
If not, I am curious how _uuid.c is used - because ./Lib/test/test_uuid.py does
not seem to be successful in finding it:
> /data/prj/python/git/python3-3.7/Lib/test/test_uuid.py(10)<module>()
-> py_uuid = support.import_fresh_module('uuid', blocked=['_uuid'])
(Pdb) n
> /data/prj/python/git/python3-3.7/Lib/test/test_uuid.py(11)<module>()
-> c_uuid = support.import_fresh_module('uuid', fresh=['_uuid'])
(Pdb) n
> /data/prj/python/git/python3-3.7/Lib/test/test_uuid.py(14)<module>()
-> def importable(name):
(Pdb) py_uuid
<module 'uuid' from '/data/prj/python/git/python3-3.7/Lib/uuid.py'>
(Pdb) c_uuid
(Pdb)
So, for now it seems the test is only testing 'uuid.py'. I would like to see
the added value of having gotten the _uuid Module to build.
However, if this is 'working as designed' I not worry about it and just go back
into the util.py - getnode() etc.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue28009>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
