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 benliles
Recipients benliles
Date 2009-08-17.20:23:20
SpamBayes Score 2.2252312e-05
Marked as misclassified No
Message-id <1250540601.66.0.070668154898.issue6720@psf.upfronthosting.co.za>
In-reply-to
Content
In the backport package of the multiprocessing library. A bug was
introduced in version 2.6.2.1 when the logging module was modified. If
you use logging in the backport, you get the following:

Traceback (most recent call last):
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/logging/__init__.py",
line 744, in emit
    msg = self.format(record)
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/logging/__init__.py",
line 630, in format
    return fmt.format(record)
  File
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/logging/__init__.py",
line 421, in format
    s = self._fmt % record.__dict__
KeyError: 'processName'
History
Date User Action Args
2009-08-17 20:23:21benlilessetrecipients: + benliles
2009-08-17 20:23:21benlilessetmessageid: <1250540601.66.0.070668154898.issue6720@psf.upfronthosting.co.za>
2009-08-17 20:23:20benlileslinkissue6720 messages
2009-08-17 20:23:20benlilescreate