Cédric Cabessa <cedric.cabe...@gmail.com> added the comment: > Is there are reason your validator doesn't use uuid.UUID to normalize the > value? That is, whatever the customer provides, why not use the result of > stringifying the resulting UUID
Yes, this is exactly what we do now However this behaviour is a bit surprising, we were thinking that uuid.UUID could be used as a validator I understand the risk of breaking existing code with a fix that enforce a strict form. Maybe a line should be added in the documentation to prevent people using this as a validator without more check? But ok, you can close the bug if you prefer ... I think there no perfect solution :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36757> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
