Issue 4078: asyncore fixes are not backwards compatible (original) (raw)

Issue4078

Created on 2008-10-08 18:04 by sidnei, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg74540 - (view)	Author: Sidnei da Silva (sidnei)	Date: 2008-10-08 18:04
I am working on getting Zope to run (or at least, start) with Python 2.6. It actually starts right now after applying some patches, which is amazing on itself, but it dies right away due to changes in asyncore that break Zope's internal version of medusa. I've opened a bug against Zope on Launchpad, but someone suggested that it might actually be a bug in python, in the sense that it changed asyncore in a backwards-incompatible way. I wouldn't go that far, since I think it's more likely that Zope's version of medusa is poking into asyncore internals instead. Here's the bug, for reference: https://bugs.launchpad.net/zope2/+bug/280020 I suspect a change similar to this will need to be applied to medusa: http://codereview.appspot.com/744/diff/1/23 I'm puzzled though as to why the change is incompatible. I would have expected at least some kind of deprecation warning on Python 2.5. Either way, if you think the issue needs to be fixed in medusa feel free to close this bug.
msg74547 - (view)	Author: Josiah Carlson (josiahcarlson) *	Date: 2008-10-08 21:21
Zope's medusa was relying on internal details of asyncore (the ac_out_buffer attribute), which is no longer applicable. It also seems as though much of medusa itself borrows from asynchat.async_chat, which suggests that it should subclass there.
msg124478 - (view)	Author: R. David Murray (r.david.murray) *	Date: 2010-12-22 02:46
Looks like Josiah just forgot to close this bug, so I'm closing it.