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 dursobr
Recipients dursobr, georg.brandl
Date 2008-11-11.19:04:00
SpamBayes Score 1.1078374e-05
Marked as misclassified No
Message-id <1226430242.52.0.860879245755.issue4300@psf.upfronthosting.co.za>
In-reply-to
Content
the 2.6 docs for the multiprocessing module have a minor error in the
logging example which causes it to fail:

the documentation says to get the logger with
'multiprocessing.get_logger()' which works

but the example uses 'multiprocessing.getLogger()' which uses the
logging package method name and is not valid.

The full example in the docs is:

>>> import multiprocessing, logging
>>> logger = multiprocessing.getLogger()
>>> logger.setLevel(logging.INFO)
>>> logger.warning('doomed')
[WARNING/MainProcess] doomed
>>> m = multiprocessing.Manager()
[INFO/SyncManager-1] child process calling self.run()
[INFO/SyncManager-1] manager bound to '\\\\.\\pipe\\pyc-2776-0-lj0tfa'
>>> del m
[INFO/MainProcess] sending shutdown message to manager
[INFO/SyncManager-1] manager exiting with exitcode 0
History
Date User Action Args
2008-11-11 19:04:02dursobrsetrecipients: + dursobr, georg.brandl
2008-11-11 19:04:02dursobrsetmessageid: <1226430242.52.0.860879245755.issue4300@psf.upfronthosting.co.za>
2008-11-11 19:04:01dursobrlinkissue4300 messages
2008-11-11 19:04:00dursobrcreate