#25410: Empty ClearableFileInput raises ValueError
---------------------------------+-------------------------------------
     Reporter:  vfigueiro        |                    Owner:  timgraham
         Type:  Bug              |                   Status:  assigned
    Component:  Forms            |                  Version:  master
     Severity:  Release blocker  |               Resolution:
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+-------------------------------------
Changes (by timgraham):

 * status:  new => assigned
 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * component:  Uncategorized => Forms
 * needs_tests:   => 0
 * owner:  nobody => timgraham
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Old description:

> Having an empty file field raises ValueError whenever the
> ClearableFileInput widget is rendered in the admin or in a custom form.
> It prevents the rendering of the form in change mode (works in creation
> mode).
>
> I guess this started happening on Python 2.7 after #24727 was fixed
> (5c412dd).
>
> Related ticket: #13327

New description:

 Having an empty file field raises ValueError whenever the
 ClearableFileInput widget is rendered in the admin or in a custom form. It
 prevents the rendering of the form in change mode (works in creation
 mode).

 I guess this started happening on Python 2.7 after #24727 was fixed
 [5c412dd].

 Related ticket: #13327

--

Comment:

 Confirmed as a regression in 1.9. I'll revert the patch that caused the
 regression, reopen that ticket for more investigation, and add a test for
 this issue.

--
Ticket URL: <https://code.djangoproject.com/ticket/25410#comment:1>
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/067.e1c91dd70f489f0a28189aa07a7b880e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to