#30114: ValidationError sometimes raised for valid UUIDs with mod_wsgi
-------------------------------------+-------------------------------------
Reporter: Jerry Vinokurov | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: validationerror, | Triage Stage:
uuid | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Hi @treager — sorry you're hitting problems here, but I can't see anything
that pins down an issue in Django. (There's just too many variables in the
two set-ups you describe to see that that's the case.)
Please see the comments and links preceding
[https://code.djangoproject.com/ticket/30114#comment:4 Keryn's
conclusion]:
> AFAIK there was nothing in Django at fault, and nothing Django could do
to fix or even warn about it.
Then, you decribe this:
> ... is an UUID object but not of instance uuid.UUID as described above.
In normal play, how is this possible?:
What we need to be able to address this (if there's an issue in Django) is
a minimal reproduce project that shows this coming up.
I hope that makes sense. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/30114#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.73453720a0f8daa6c1598228423e165e%40djangoproject.com.