#3989: Django seems to parse only the addr-spec production of RFC 2822
-------------------------------------------------------------+--------------
Reporter: Pierre Thierry <[EMAIL PROTECTED]> | Owner:
nobody
Status: new |
Component: Validators
Version: SVN |
Resolution:
Keywords: |
Stage: Design decision needed
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 1 |
Needs_better_patch: 0
-------------------------------------------------------------+--------------
Comment (by Vinay Sajip <[EMAIL PROTECTED]>):
The DRY principle, if I'm not misapplying it, seems to lead to the
conclusion that
{{{
email = EmailField(allow_display_name=True)
}}}
would be the best solution - having the default as {{{False}}} allows the
behaviour to remain as it is currently, but which can be modified easily
by setting {{{allow_display_name=True}}} where the use case warrants it.
With the two-field solution, any future change to the {{{EmailField}}}
needs to potentially be duplicated in {{{EmailWithoutDisplayNameField}}}.
And there's not enough difference in behaviour between the two, IMO, to
warrant two classes.
--
Ticket URL: <http://code.djangoproject.com/ticket/3989#comment:18>
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
-~----------~----~----~----~------~----~------~--~---
