➜

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.03:36:40
SpamBayes Score 0.00086492865
Marked as misclassified No
Message-id <1238557002.38.0.779036749599.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content 
At the language summit last Thursday there was widespread disappointment
with the changes to asyncore.py in 2.6, which broke almost all code that
actually uses it.  Unfortunately, the documented API is lame, so
everybody depended on undocumented internals, and those were changed
without respect for established use.  I'd like to prevent more problems
like that.
History
Date User Action Args
2009-04-01 03:36:42gvanrossumsetrecipients: + gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, forest, giampaolo.rodola, kevinwatters, djarb, markb, intgr
2009-04-01 03:36:42gvanrossumsetmessageid: <1238557002.38.0.779036749599.issue1641@psf.upfronthosting.co.za>
2009-04-01 03:36:41gvanrossumlinkissue1641 messages
2009-04-01 03:36:40gvanrossumcreate