#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 gwilson):
Yes, I understand that you can use anything for the display name. My
point was simply that one might not always want to allow display names, as
is the case with every use of the `EmailField` in code I've written. I do
think that allowing for display names would be a welcome feature, I just
think that the developer should be able to specify which format is
allowable since each has its valid use cases. I also think that separate
fields (i.e. `EmailField` and `EmailWithDisplayNameField`) would be better
than adding an option to the existing `EmailField` (i.e. `email =
EmailField(allow_display_name=True)`) or changing the current behavior of
`EmailField` without allowing for the address-only form of entry.
--
Ticket URL: <http://code.djangoproject.com/ticket/3989#comment:17>
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
-~----------~----~----~----~------~----~------~--~---
