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 jnoller
Recipients amaury.forgeotdarc, benjamin.peterson, gvanrossum, jnoller, pitrou, pjenvey, r.david.murray, vinay.sajip
Date 2009-10-14.23:44:25
SpamBayes Score 2.991108e-06
Marked as misclassified No
Message-id <1255563866.46.0.888739761608.issue7120@psf.upfronthosting.co.za>
In-reply-to
Content
>The addition of multiprocessing support to logging seems to have 
happened 
> in 2.6.2; bad timing for a feature. :-(

Just in minor self-defense, this wasn't a feature, it was a bug fix. The 
original multiprocessing code base relied on some unfortunate monkey-
patching of the logging module to insert itself into the logging module. 
That code was broken in the merge into 2.6, and I didn't catch it. So, I 
felt this was a bug fix, and not a feature-add.

I apologize for this.
History
Date User Action Args
2009-10-14 23:44:26jnollersetrecipients: + jnoller, gvanrossum, vinay.sajip, amaury.forgeotdarc, pitrou, pjenvey, benjamin.peterson, r.david.murray
2009-10-14 23:44:26jnollersetmessageid: <1255563866.46.0.888739761608.issue7120@psf.upfronthosting.co.za>
2009-10-14 23:44:25jnollerlinkissue7120 messages
2009-10-14 23:44:25jnollercreate