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'
As far as I know, the only 2.5 issues that will get fixed are security issues, and this is not marked as such. So the question for Christian is whether this is an exception. Or is this even an issue for this tracker?
The backport of multiprocessing is currently stale; and there are a few bugs in the tracker assigned to christian or myself in regards to it. If it's not too much trouble, I'd leave this one alone until the exact future of the backport can be resolved.