➜

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 gvanrossum
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, jafo, josiahcarlson, kevinwatters, markb
Date 2009-04-01.22:01:29
SpamBayes Score 1.9257109e-06
Marked as misclassified No
Message-id <1238623291.71.0.123243289406.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content 
Well arguably asyncore is unsalvageable due to the undocumented
internals issue, and we sure know a bit more about how to design a
*good* asynchronous API than we did when asyncore was created. (One
hint: don't make subclassing part of your API.)

The Zope folks at the meeting in all seriousness proposed reverting to
the 2.5 version of asyncore since "it is broken in 2.6".  Since I don't
use it myself I really have no idea if anyone is using the 2.6 version.
History
Date User Action Args
2009-04-01 22:01:32gvanrossumsetrecipients: + gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, forest, giampaolo.rodola, kevinwatters, djarb, markb, intgr
2009-04-01 22:01:31gvanrossumsetmessageid: <1238623291.71.0.123243289406.issue1641@psf.upfronthosting.co.za>
2009-04-01 22:01:30gvanrossumlinkissue1641 messages
2009-04-01 22:01:29gvanrossumcreate