Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#14860 closed (fixed)

Various PL localflavor fields don't handle EMPTY_VALUES correctly

Reported by: idangazit Owned by: idangazit
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)

14860.diff (1.5 KB) - added by idangazit 4 years ago.

Download all attachments as: .zip

Change History (5)

Changed 4 years ago by idangazit

comment:1 Changed 4 years ago by idangazit

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Status changed from new to assigned

comment:2 Changed 4 years ago by idangazit

  • Triage Stage changed from Unreviewed to Accepted

comment:3 Changed 4 years ago by Alex

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [14949]) Fixed #14860 -- PLPESELField, PLNIPField, and PLREGONField didn't handle all EMPTY_VALUES correctly. Also converted teh Polish localflavor doctests into unittests. We have always been at war with doctests. Thanks to Idan Gazit.

comment:4 Changed 4 years ago by Alex

(In [14973]) [1.2.X] Fixed #14860 -- PLPESELField, PLNIPField, and PLREGONField didn't handle all EMPTY_VALUES correctly. Also converted teh Polish localflavor doctests into unittests. We have always been at war with doctests. Thanks to Idan Gazit. Backport of [14949].

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