[issue4078] asyncore fixes are not backwards compatible

R. David Murray added the comment: Looks like Josiah just forgot to close this bug, so I'm closing it. -- nosy: +r.david.murray stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue4078] asyncore fixes are not backwards compatible

Josiah Carlson <[EMAIL PROTECTED]> added the comment: 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

[issue4078] asyncore fixes are not backwards compatible

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> josiahcarlson nosy: +josiahcarlson ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4078] asyncore fixes are not backwards compatible

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- nosy: +giampaolo.rodola, josiah.carlson ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4078] asyncore fixes are not backwards compatible

New submission from Sidnei da Silva <[EMAIL PROTECTED]>: 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 ver