Nick Edds <[EMAIL PROTECTED]> added the comment: I've been thinking about this a bit, and I don't see how handling it should be all that different from handling module renaming.
For import UserDict, we can just change UserDict to collections and deal with UserDict.UserDict with a deprecation warning and UserDict.IterableUserDict and UserDict.Mixin with transformations to collections.UserDict and collections.MutableMapping. For from imports, we can raise the deprecation warning on UserDict, and otherwise change from UserDict import ... to from collections import ... and then for non-import appearances of UserDict, IterableUserDict, and Mixin rename or raise a deprecation warning as appropriate. For the other import cases, similar things could be done. I think the old version of fix_imports, which had support like this, would basically be all that we need. I should be able to mimic that functionality, but also make it more scalable than the previous version. Is there something I'm missing here about the difference between modules and classes? From the use-cases I've observed of UserDict, it seems like this functionality would be sufficient. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2876> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
