[issue4078] asyncore fixes are not backwards compatible

Sidnei da Silva report at bugs.python.org
Wed Oct 8 20:04:46 CEST 2008

New submission from Sidnei da Silva <sidnei.da.silva at gmail.com>:

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:


I suspect a change similar to this will need to be applied to medusa:


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.

components: Library (Lib)
messages: 74540
nosy: sidnei
severity: normal
status: open
title: asyncore fixes are not backwards compatible
type: behavior
versions: Python 2.6

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list