#4542: AU localflavor date field
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component:
django.contrib.localflavor
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
We should probably give these better names, since they aren't specific to
Australia. The North American format is by far the minority case.
The settings aren't a good idea, because it will conflict with far too
many places where there are existing date format strings and we'll be
fielding actual and perceived bug reports until the cows come home. Plus,
again, they aren't .au specific.
We might make a "generic" directory (or similar name) under localflavor/
for this sort of thing. Then the classes can just be called !DateField and
!DateTimeField (because the import location namespaces them sufficiently).
Patch is missing tests, too.
--
Ticket URL: <http://code.djangoproject.com/ticket/4542#comment:3>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
