Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#14859 closed (fixed)

Various IT localflavor fields don't handle EMPTY_VALUES correctly

Reported by: Idan Gazit Owned by: Idan Gazit
Component: contrib.localflavor Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Fields with required=False should not choke while cleaning any value in EMPTY_VALUES (from django.core.validators):

EMPTY_VALUES = (None, , [], (), {})

Attachments (1)

14859.diff (935 bytes) - added by Idan Gazit 6 years ago.

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by Idan Gazit

Attachment: 14859.diff added

comment:1 Changed 6 years ago by Idan Gazit

Status: newassigned

comment:2 Changed 6 years ago by Idan Gazit

Triage Stage: UnreviewedAccepted

comment:3 Changed 6 years ago by Alex Gaynor

Resolution: fixed
Status: assignedclosed

(In [14945]) Fixed #14859 -- ITSocialSecurityNumberField and ITVatNumberField didn't handle all EMPTY_VALUES gracefully. Also converted the Italias localflavor doctests into unittests. We have always been at war with doctests. Thanks to Idan Gazit.

comment:4 Changed 6 years ago by Alex Gaynor

(In [14969]) [1.2.X] Fixed #14859 -- ITSocialSecurityNumberField and ITVatNumberField didn't handle all EMPTY_VALUES gracefully. Also converted the Italias localflavor doctests into unittests. We have always been at war with doctests. Thanks to Idan Gazit. Backport of [14945].

Note: See TracTickets for help on using tickets.
Back to Top