[issue10128] multiprocessing.Pool throws exception with __main__.py

2015-11-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 5d88c1d413b9 by Nick Coghlan in branch '2.7': Close #10128: don't rerun __main__.py in multiprocessing https://hg.python.org/cpython/rev/5d88c1d413b9 -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed

[issue10128] multiprocessing.Pool throws exception with __main__.py

2015-11-18 Thread Nick Coghlan
Nick Coghlan added the comment: Thanks for the investigation Marc. I'd been hesitant to backport the mitigation patch in #10845 to 2.7.x, (as it *does* represent a behavioural change), but if that code path is currently hitting an assert statement anyway, it seems reasonable to make the change

[issue10128] multiprocessing.Pool throws exception with __main__.py

2015-11-18 Thread Marc Schlaich
Marc Schlaich added the comment: Please see my latest comments to https://github.com/pypa/pip/issues/1891. tl;dr It is related to the -m switch as pip's wheel launcher does PYTHONPATH=script.exe python -m __main__ -- ___ Python tracker

[issue10128] multiprocessing.Pool throws exception with __main__.py

2015-02-23 Thread Marc Schlaich
Marc Schlaich added the comment: Please fix this. Scripts with multiprocessing bundled as wheels are broken with Python 2.7 on Windows: https://github.com/pypa/pip/issues/1891 -- nosy: +schlamar ___ Python tracker

[issue10128] multiprocessing.Pool throws exception with __main__.py

2014-03-12 Thread Martin Dengler
Martin Dengler added the comment: I applied the patch from #10845 to 2.7.6 and it worked well for me. -- ___ Python tracker ___ ___ Py

[issue10128] multiprocessing.Pool throws exception with __main__.py

2014-03-12 Thread Martin Dengler
Changes by Martin Dengler : -- nosy: +mdengler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue10128] multiprocessing.Pool throws exception with __main__.py

2011-12-21 Thread Nick Coghlan
Nick Coghlan added the comment: The fix from #10845 should be backported to Python 2.7 (bypassing the assertion isn't enough - you want to skip re-executing __main__ entirely) -- nosy: +ncoghlan ___ Python tracker

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-20 Thread Michael Olson
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

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-20 Thread Michael Olson
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.org/file19296/is

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-20 Thread Ask Solem
Changes by Ask Solem : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-19 Thread Michael Olson
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 __

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-19 Thread Ask Solem
Ask Solem added the comment: Is this on Windows? Does it work for you now? -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-17 Thread Michael Olson
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__. Ran a few tr

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-16 Thread R. David Murray
Changes by R. David Murray : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-16 Thread Ned Deily
Changes by Ned Deily : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue10128] multiprocessing.Pool throws exception with __main__.py

2010-10-16 Thread Michael Olson
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 prepare(preparation_data)