[issue34145] uuid3 and uuid5 hard to use portably between Python 2 and 3

Zachary Ware added the comment: Python 2.7 has reached EOL, and so this change can no longer be made. Thanks for the idea report and idea anyway, Bence! -- nosy: +zach.ware resolution: -> out of date stage: patch review -> resolved status: open -> closed versions: -Python 3.6

[issue34145] uuid3 and uuid5 hard to use portably between Python 2 and 3

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue34145] uuid3 and uuid5 hard to use portably between Python 2 and 3

Change by Braden Groom : -- keywords: +patch pull_requests: +9433 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue34145] uuid3 and uuid5 hard to use portably between Python 2 and 3

New submission from Bence Romsics : The issue I'd like to report may not be an outright bug neither in cPython 2 nor in cPython 3, but more of a wishlist item to help Python programmers writing UUID-handling code that's valid in Python 2 and 3 at the same time. Please consider these one-liner