I'll just add my 2 cents as partial copy/paste from the (now closed)
ticket page:
I agree w/ Serge that USE_L10N should be the default value for
localize.
* I think the case Russel mentions is the exception, not the rule.
"Usually" a number is just a number, not a year. Postal codes and
phone num
I have opened a ticked for this same issue, it was rejected because the
core team didn't liked the idea of including FormField options in
ModelField. Decision i think was correct, I wasnt aware the other
FormFields options in ModelFields like help_text were there for historical
reasons.
https://git
On Fri, Jun 22, 2012 at 7:23 AM, Klaas van Schelven <
klaasvanschel...@gmail.com> wrote:
> I've created a ticket, but have always understood that calling
> attention to tickets should be done separately on the Django-
> developers mailinglist
It's not necessary nor encouraged to call attention t
Hi all,
I've created a ticket, but have always understood that calling
attention to tickets should be done separately on the Django-
developers mailinglist, so allow me to copy/paste a bit:
As it is now one cannot make localized ModelForms without violating
DRY. Developers w/o the desire for loca
