logging processName is missing in 2.6.2.1

[GoogleCodeExporter]

This commit moved processName support from multiprocessing to the logging
module:
http://svn.python.org/view?view=rev&revision=68737

I've made a patch to test for processName in log records, and another to
re-add _check_logger_class, in multiprocessing.patch. _check_logger_class
isn't perfect, and issue 4301 will still be there, but the patches prevent
a regression.

(Issue 4301 means that logging initialization, like logging.basicConfig,
must be done after calling multiprocessing.get_logger)

Original issue reported on code.google.com by g2p.c...@gmail.com on 1 Aug 2009 at 4:06

Attachments:

• 0001-Test-logging-of-processName.patch
• 0002-Fix-logging-of-processName.patch

[GoogleCodeExporter]

A lot of our users are having this problem as logging is an essential part of 
celery. So maybe the priority on this 
bug should be raised, and if this patch fixes it, a new release is in order.

Original comment by askso...@gmail.com on 19 Aug 2009 at 8:10

[GoogleCodeExporter]

Agreed on the need for a new release. The current regression is due to 
unfortunate
cherry-picking, which I may have precipitated by asking for a backport and a new
release. It happened, but without a grace period between the svn backport merge 
and
the pypi upload.

Anyway, you could apply those patches and test to your heart's content. They 
are on
top of the current trunk. Trunk + these patches is a known quantity and a 
should make
a better release.

Original comment by g2p.c...@gmail.com on 19 Aug 2009 at 8:43

[GoogleCodeExporter]

It's been a while since this ticket has seen any activity, are there any 
updates here?

Original comment by mgeo...@gmail.com on 6 Apr 2010 at 4:34