This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sidnei
Recipients sidnei
Date 2008-10-08.18:04:43
SpamBayes Score 6.550316e-15
Marked as misclassified No
Message-id <1223489086.17.0.537265261375.issue4078@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2008-10-08 18:04:46sidneisetrecipients: + sidnei
2008-10-08 18:04:46sidneisetmessageid: <1223489086.17.0.537265261375.issue4078@psf.upfronthosting.co.za>
2008-10-08 18:04:45sidneilinkissue4078 messages
2008-10-08 18:04:44sidneicreate