On 11 févr. 2014, at 03:00, Russell Keith-Magee <[email protected]> wrote:
> I'd be able to mount a reasonable argument that {{ field(size=30) }} is a
> problem, not a feature (whats the magical significance of 30? What happens if
> you make a site-wide decision to extend all size=30 fields to size=40? etc.
> And, to be clear, I'm not interested in having *this* specific argument in
> long form. Just be aware that I'd make it, and that it's the argument that
> underpins the original design decisions of Django's template language).
With all due respect, you can find a better argument... Everyone will hardcode
the 30 in Python code just as well as in template code...
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/8BE54FE4-8898-4C3B-8731-DD8B5A75B5E3%40polytechnique.org.
For more options, visit https://groups.google.com/groups/opt_out.
