maxlength deprecation warning

[GoogleCodeExporter]

The latest dbsettings revision does not conform to the recent keyword 
change in Django: maxlength should be named max_length.

The following deprecation warnings are printed:
dbsettings/models.py:11: DeprecationWarning: maxlength is deprecated. Use 
max_length instead.
  module_name = models.CharField(maxlength=255)
...

Original issue reported on code.google.com by iar.seme...@gmail.com on 18 Dec 2007 at 3:57

[GoogleCodeExporter]

This was expected, but I'm not sure I'm willing to make the change quite yet. 
Doing
so would require a more recent SVN checkout solely to suppress this warning, 
and that
doesn't seem worth it at this point. I'll more likely fix this under whichever 
of the
following conditions comes first:

* A new Django release makes max_length standard for an official distribution, 
so I
can just require that version.
* Another trunk feature is useful for dbsettings, forcing me to require a more 
recent
checkout anyway.

Until either of those things, though, I think I can live with people seeing a 
single
deprecation warning, so I don't have to require quite as recent a checkout.

Original comment by gulop...@gmail.com on 18 Dec 2007 at 4:12

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Sep/3 we have another Django official release: 1.0

Here comes my patch to work with it:

Original comment by alan.jus...@gmail.com on 12 Sep 2008 at 1:12

Attachments:

• django1_0_fix.patch

[GoogleCodeExporter]

Issue 17 has been merged into this issue.

Original comment by gulop...@gmail.com on 25 Nov 2008 at 5:01

[GoogleCodeExporter]

Here's an updated Django 1.0 patch file.  The only difference between this one 
and the one from silva is that this 
patch includes the updated Signals call.

Original comment by treborhu...@gmail.com on 30 Dec 2008 at 9:33

Attachments:

• dbsettings-1.0.patch