New submission from Skip Montanaro <[EMAIL PROTECTED]>:
I worked up a simple example of using the external processing module
(0.52) for a friend at work today. I noticed some cases where it raised
exceptions during exit. Not all the time, but not infrequently either.
This evening I tweaked it for the 2.6 multiprocessing module's API and
tried it out. I ran it in a large loop:
for i in $(range 500) ; do
echo '!'$i
python test_proc.py
end | egrep '!'
Most of the time all I see are the '!' lines from the echo command.
Every once in awhile I see a traceback though. For example:
Exception in thread QueueFeederThread (most likely raised during
interpreter shutdown):
Traceback (most recent call last):
File "/Users/skip/local/lib/python2.7/threading.py", line 522, in
__bootstrap_inner
File "/Users/skip/local/lib/python2.7/threading.py", line 477, in run
File "/Users/skip/local/lib/python2.7/multiprocessing/queues.py", line
233, in _feed
<type 'exceptions.TypeError'>: 'NoneType' object is not callable
This occurred once in approximately 1500 runs of the script (three times
through the above shell loop). The script used to trigger this
exception is attached.
----------
components: Library (Lib)
files: test_proc.py
messages: 74656
nosy: skip.montanaro
priority: normal
severity: normal
status: open
title: multiprocessing occasionally spits out exception during shutdown
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file11771/test_proc.py
_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4106>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
