[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

R. David Murray report at bugs.python.org
Wed Apr 21 19:51:26 CEST 2010


R. David Murray <rdmurray at bitdance.com> added the comment:

Well, the attribute error message could be fixed, too, by enclosing the forwarding getattr in a try/except and generating the "correct" attribute error text.

Changing the forwarding behavior itself is the kind of issue that would need to be discussed on python-dev, and we'd need to make sure that the various asyncore constiuencies got a chance to chime in (remember the previous breakage of asyncore monkey-patching in 2.6 and the rancor it caused).  My guess is that we can't change it, though.  Certainly not in 2.7.

I'm changing the title of the issue to more accurately reflect the discussion.

----------
priority: low -> normal
title: asyncore.dispatcher.__repr__() is weird -> asyncore.dispatcher's __getattr__ method produces confusing effects

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8483>
_______________________________________


More information about the Python-bugs-list mailing list