On Jun 16, 6:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > However all that is beside the point. The patch that Jonas has posted in
> > #4590 is just to change the default settings. I'm not sure if that's
> > worth doing or not. Currently I'm somewhere between -0 and +0, since
> > it's completely within the control of the application user, so it's
> > basically a non-event (also the patch should have been against
> > global_settings.py, not settings.py, but that's a minor thing).
>
> Yeah, I started writing my reply before I saw the follow-up patch.
>
> Looking at what's come up since then, I feel like this is a bikeshed
> problem and probably not worth spending time on; the fact that default
> formats are within the control of the person deploying Django (through
> documented settings), and easily overridden on a case-by-case basis
> (through explicit date format strings when needed, as in template
> output), says to me that this isn't a big deal and that the default is
> pretty much arbitrary.
>
> So I'd be -0 at best here; replacing one arbitrary default with
> another arbitrary default doesn't strike me as a particularly pressing
> change ;)
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
The dateformat year, month, day or year, day, month should be part of
each language translation and have a default.
The problem with explicit is if you have a multilanguage project you
can't make it pick the correct one easily.
+0.5
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
