#17627: contrib.admin.util is misnamed
--------------------------------------+------------------------------------
     Reporter:  PaulM                 |                    Owner:  lukegb
         Type:  Cleanup/optimization  |                   Status:  assigned
    Component:  contrib.admin         |                  Version:  SVN
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  1                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by lukegb):

 Replying to [comment:15 russellm]:
 > On a related note -- if you want to make this a really sweet target for
 commit, you could also address the other instances of util.py in the
 source tree.

 Done in the latest version (0002.patch) of my patch.

 Side notes which break backwards compatibility:
 Code which does
 {{{#!python
 from django.db import utils
 from django.db.backends import *
 }}}
 will break with this change, as django.db.backends.utils will overwrite
 django.db.utils. Not sure how to fix this, but I fixed it in the instances
 where Django does it:
 * django/db/backends/mysql/base.py
 * django/db/backends/oracle/base.py
 * django/db/backends/postgresql_psycopg2/base.py
 * django/db/backends/sqlite3/base.py

 (just realised I forgot to update the deprecation notes - new patch
 incoming)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17627#comment:16>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to