#27148: Invalid input for UUIDField with ModelMultipleChoiceField throws
ValueError, not ValidationError
-------------------------------+------------------------------------
     Reporter:  Daniel Hahler  |                    Owner:  nobody
         Type:  Bug            |                   Status:  closed
    Component:  Forms          |                  Version:  1.10
     Severity:  Normal         |               Resolution:  fixed
     Keywords:                 |             Triage Stage:  Accepted
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"4101b57b1984af7f63eb5c7832861c30f2e7642d" 4101b57]:
 {{{
 #!CommitTicketReference repository=""
 revision="4101b57b1984af7f63eb5c7832861c30f2e7642d"
 [1.11.x] Refs #27148 -- Fixed UUIDField.to_python(None) crash.

 Regression in 2f9861d823620da7ecb291a8f005f53da12b1e89.

 Backport of d26413113c1a5c95218fe4e43a684a2fe1ad1bff from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/27148#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ece18f0a835b8498191dd53e4995272c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to