Author josiahcarlson
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, jafo, josiahcarlson, kevinwatters, markb
Date 2009-04-01.18:28:55
SpamBayes Score 2.2797e-05
Marked as misclassified No
Message-id <1238610536.72.0.870165632909.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content
I'm happy to let them know proposed changes now that I know issues 
exist, but you have to admit that they were pretty under-the-radar until 
4-5 months *after* 2.6 was released.  If there is a mailing address that 
I can send proposed changes to asyncore so that they can have a say, I'd 
be happy to talk to them.

Generally, what you are saying is that I'm damned if I do, damned if I 
don't.  By taking ownership and attempting to fix and improve the module 
for 2.6 (because there were a bunch of outstanding issues), people are 
pissed (generally those who use Zope and/or medusa).  Despite this, 
other people have continued to use it, and have been pushing for new 
features; event scheduling being one of the major parts.

Pulling asyncore out of Python is silly.  Not improving the module 
because of fear of breakage is silly.  I'm happy to hear suggestions 
from the Zope crew, but I'm only going to put as much effort in 
communicating with them as they do me.
History
Date User Action Args
2009-04-01 18:28:56josiahcarlsonsetrecipients: + josiahcarlson, gvanrossum, akuchling, facundobatista, jafo, forest, giampaolo.rodola, kevinwatters, djarb, markb, intgr
2009-04-01 18:28:56josiahcarlsonsetmessageid: <1238610536.72.0.870165632909.issue1641@psf.upfronthosting.co.za>
2009-04-01 18:28:55josiahcarlsonlinkissue1641 messages
2009-04-01 18:28:55josiahcarlsoncreate