Bluebird75 added the comment: This issue is closed, but the problems remain that the current version of winpdb is incompatible with django + python 2.7 .
I don't really understsand why the issue is closed without any change to python logging library itself. To sum-up the issue: 1. django uses some standard interface of logging 2. winpdb replaces the builtin __import__ with a custom python function 3. logging stores the __import__ value in a class attribute 4. python calls class attributes differently whether they are a builtin function (direct function call) or python function (which becomes a bound method, receiving self as first argument). The problem comes from point 4, but the root of the problem is that logging assumes that it is always storing a builtin function. The documentation fix does not fix the problem. How could winpdb apply this fix ? Should it check that the argument passed to its import replacement are not by mistake a DictConfigurator instance (bound method of logging class) ? That sounds like an ugly workaround for a problem lying in python logging module. The correct fix is that logging should not assume importer to be a builtin function and add some flexibility around this. ---------- nosy: +Bluebird75 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12718> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
