➜

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 josiahcarlson
Recipients ajaksu2, akuchling, anadelonbrin, brett.cannon, giampaolo.rodola, josiahcarlson, tim.peters
Date 2009-02-12.05:03:40
SpamBayes Score 2.2849488e-06
Marked as misclassified No
Message-id <1234415021.95.0.2916320635.issue1161031@psf.upfronthosting.co.za>
In-reply-to
Content 
Considering that we're looking at 2.7 and 3.1, I think that  
(paraphrased) "logging fallout from changes to 2.4" are a bit out-of-
date.  People who have continued to use asyncore/asynchat in the last 4 
years have already changed their code.  People who write new code 
already deal with the logging.

Does anyone have a compelling reason as to why we shouldn't just close 
this bug?
History
Date User Action Args
2009-02-12 05:03:42josiahcarlsonsetrecipients: + josiahcarlson, tim.peters, akuchling, brett.cannon, anadelonbrin, giampaolo.rodola, ajaksu2
2009-02-12 05:03:41josiahcarlsonsetmessageid: <1234415021.95.0.2916320635.issue1161031@psf.upfronthosting.co.za>
2009-02-12 05:03:40josiahcarlsonlinkissue1161031 messages
2009-02-12 05:03:40josiahcarlsoncreate