#17870: Documentation for EmailField max_length
-------------------------------------+-------------------------------------
Reporter: Rotund | Owner: Rotund
Type: Bug | Status: new
Component: Documentation | Version:
Severity: Normal | 1.4-beta-1
Keywords: | Resolution:
Has patch: 0 | Triage Stage: Ready for
Needs tests: 0 | checkin
Easy pickings: 1 | Needs documentation: 0
| Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Ready for checkin
* needs_tests: => 0
* needs_docs: => 0
Comment:
To be clear: the proposal is to add the new text as a a note/admonition to
[https://docs.djangoproject.com/en/1.3/ref/models/fields/#emailfield the
EmailField API reference]. Marking RFC because it's a simple addition, and
it's worth pointing out this constraint.
However, I'd slightly modify the text:
The default 75 character max_length is not capable of storing all possible
RFC3696/5321-compliant email addresses. In order to store all possible
valid email addresses, a max_length of 254 is required. The default
``max_length`` of 75 exists for historical reasons. The default has not
been changed in order to maintain backwards compatibility with existing
uses of EmailField.
--
Ticket URL: <https://code.djangoproject.com/ticket/17870#comment:1>
Django <https://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.
