Giampaolo Rodola' <billiej...@users.sourceforge.net> added the comment:
I don't know what are the problems experienced by the Zope folks (is there a place where this is discussed?) but I can guess that they're having problems with asynchat rather than with asyncore, since the latter hasn't changed too much between 2.5 and 2.6 except for low level connection related bug fixes. The greatest difference in the new asynchat is that the producer_fifo attribute is no longer an asyncore.fifo() instance but a deque(). Python 2.5: > self.producer_fifo = fifo() Python 2.6 > self.producer_fifo = deque() Although they're quite similar the old code relying on the fifo() API can't obviously work anymore. This could have been a bad choice and there are probably other changes that might have caused the problem (one other change that comes to my mind is the different readable() writable() implementation). An alternative to completely reverting asynchat.py to the 2.5 version, which is somewhat too drastic IMO, could be identifying what are the changes that caused the incompatibility, and reverting those parts only for 2.6.2, in a way that no one (2.5 and 2.6 users) is affected. If there's a place where this is discussed I could contribute in some way since I've been working on asynchat/asyncore for a long time now. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1641> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
