#3989: Django seems to parse only the addr-spec production of RFC 2822
-------------------------------------------------------------+--------------
Reporter: Pierre Thierry <[EMAIL PROTECTED]> | Owner:
adrian
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]>):
Although of course it's conventional to use firstname/lastname as the
display name, it's not mandated - for example, a nickname could be used as
the display name, or a suffix such as " (Home)" or " (Work)" might be
appended to the user's name to form the display name. So the display name
is logically a different value from the user's name, even if it has the
same value for most users.
For this reason, I don't think having two fields makes sense, though it
may be sensible to increase the size of the email field (there's a
separate discussion about this on the mailing lists, not related to
display name support).
--
Ticket URL: <http://code.djangoproject.com/ticket/3989#comment:16>
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
-~----------~----~----~----~------~----~------~--~---
