Michael Olson added the comment:
As a note, I didn't attach a patch at first because I was fairly sure I was
kludging it into submission, but at least this makes it clear as to what I did.
v/r
-- Michael Olson
--
___
Python tracker
Michael Olson added the comment:
Ummm, I think I've been unclear on where I was making changes, I changed
lib\multiprocessing\forking.py to fix the issue.
Patch attached.
--
keywords: +patch
resolution: invalid ->
status: closed -> open
Added file: http://bugs.python.or
Michael Olson added the comment:
Sorry about that, yes, this is on Windows XP and 7, 32 bit.
And with the if statement it seems to work fine.
v/r
-- Michael Olson
--
___
Python tracker
<http://bugs.python.org/issue10
Michael Olson added the comment:
I wrapped the offending assertion in a if main_name != '__main__'. I considered
not checking the module_name against built-in modules but that seemed likely to
be the sort of thing being guarded against, so I left it at an exception for
__main__.
New submission from Michael Olson :
In an application with an entry point of __main__.py, multiprocessing.Pool
throws the following:
Traceback (most recent call last):
File "", line 1, in
File "D:\Dev\Python27\lib\multiprocessing\forking.py", line 346, in main
prep
New submission from Michael Olson :
Using Python 2.7 x32 on Windows XP
Attempting to create a multiprocessing.pool.ThreadPool
in a child thread created using threading.Thread, an
AttributeError is thrown. A ThreadPool created in the
main thread can be passed to the child thread and used
