Michael Olson ol...@irinim.net 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
Michael Olson ol...@irinim.net 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 ol...@irinim.net 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 rep...@bugs.python.org
http://bugs.python.org
Michael Olson ol...@irinim.net 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
New submission from Michael Olson ol...@irinim.net:
In an application with an entry point of __main__.py, multiprocessing.Pool
throws the following:
Traceback (most recent call last):
File string, line 1, in module
File D:\Dev\Python27\lib\multiprocessing\forking.py, line 346, in main
New submission from Michael Olson ol...@irinim.net:
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
