Author josiahcarlson
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, jafo, josiahcarlson, kevinwatters, markb
Date 2009-04-01.17:12:58
SpamBayes Score 3.57719e-12
Marked as misclassified No
Message-id <1238605981.29.0.0884647818268.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content
IIRC, there was a threat to remove asyncore because there were no 
maintainers, no one was fixing bugs, no one was improving it, and no one 
was really using it (I believe the claim was that people were just using 
Twisted).  The patches that were ultimately committed to 2.6 and 3.0 
were committed 3 months prior to 2.6 release, after having languished 
for over a year because no one would review them.  If people care about 
where asyncore/asynchat are going, then it is *their* responsibility to 
at least make an effort in paying attention at least once every few 
months or so.

The delayed calls feature discussed in the current bug doesn't alter the 
behavior of previously existing code, except there are additional checks 
for pending tasks to be executed.  If people never use the call_later() 
API, it is unlikely they will experience any difference in behavior.

If you are concerned about the sched module, I'd be happy to do a search 
for it's use to verify that people aren't relying on it's internal 
implementation, only the features of it's external API.
History
Date User Action Args
2009-04-01 17:13:01josiahcarlsonsetrecipients: + josiahcarlson, gvanrossum, akuchling, facundobatista, jafo, forest, giampaolo.rodola, kevinwatters, djarb, markb, intgr
2009-04-01 17:13:01josiahcarlsonsetmessageid: <1238605981.29.0.0884647818268.issue1641@psf.upfronthosting.co.za>
2009-04-01 17:13:00josiahcarlsonlinkissue1641 messages
2009-04-01 17:12:58josiahcarlsoncreate