You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/josiahcarlson'closed_at=<Date2010-12-22.02:46:05.699>created_at=<Date2008-10-08.18:04:45.548>labels= ['type-bug', 'library']
title='asyncore fixes are not backwards compatible'updated_at=<Date2010-12-22.02:46:05.697>user='https://bugs.python.org/sidnei'
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.
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.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: