#2101: maxlength should be max_length
------------------------------------+---------------------------------------
Reporter: nirvdrum | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: maxlength max_length | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Changes (by SmileyChris):
* has_patch: 0 => 1
* stage: Design decision needed => Accepted
Comment:
From memory, Adrian said in a groups post that it's going this way so I'll
accept.
Better than that, though. I'll attach a complete patch. :)
* Changes `db.models` fields to use `max_length` (supporting full legacy
use of `maxlength`)
* Changes `oldforms` fields to use `max_length` (supporting full legacy
use of `maxlength`) also creating the legacy `maxlength` argument to the
end of all relevant `__init__`s so positional calling won't be affected
* Preserves HTML `maxlength` for field rendering
* Changes all references throughout the rest of Django to use
`max_length` (documentation, contrib, etc)
* Provides relevant regression tests
--
Ticket URL: <http://code.djangoproject.com/ticket/2101#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
