Opened 6 years ago

Closed 6 years ago

#11787 closed (wontfix)

additional fields

Reported by: Hinnack Owned by: nobody
Component: contrib.localflavor Version: 1.1
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


I wonder if the following fields do not belong here, too:

  • money sign (printable and iso) => EUR and €
  • money format (even negative)
  • number format (even negative)
  • date format(s)
  • timezones available in the country

maybe even:

  • country names in local language
  • international phone number prefixes

Change History (1)

comment:1 Changed 6 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

I'm going to mark this wontfix, on the basis that the valid choices for these fields aren't something we can really specify on a universal basis - for example, what choices should Django make available for a "MoneySignField"? $ + €? Should we differentiate between AU $ and US $ and CA $ and NZ $ and HK $? What about Rupees? Baht?

This is something that should be determined on a per-project basis, and it isn't so hard to implement that putting it in Django will save that much effort.

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