Cédric Cabessa 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
New submission from Cédric Cabessa :
UUID constructor accept string with too many dashes or keyword like urn: / uuid:
For eg, this code do not raise
```
>>> import uuid
>>> uuid.UUID('0be--468urn:urn:urn:urn:54-4bf9-41--d4-9697-41d735uuid:4fbe85uuid:')
UUID('0be46
