#11787: additional fields
-------------------------------------------------+--------------------------
Reporter: Hinnack | Owner: nobody
Status: closed | Milestone:
Component: django.contrib.localflavor | Version: 1.1
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------+--------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/11787#comment:1>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
