[issue11969] Can't launch multiproccessing.Process on methods

Antoine Pitrou added the comment: Pickling of builtin functions and methods was indeed improved thanks to __qualname__ support. Closing. -- nosy: +pitrou resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tra

[issue11969] Can't launch multiproccessing.Process on methods

Ram Rachum added the comment: Confirmed here it's working in Python 3.4, I guess it was fixed sometime in the last few years. I guess the only thing we'd care about now is ensuring a test for this was added to the test suite, so there wouldn't be a regression. Can anyone confirm that? --

[issue11969] Can't launch multiproccessing.Process on methods

Mark Lawrence added the comment: This works perfectly on 64 bit Windows 8.1 for 3.4.1 and 3.5.0a0. -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue11969] Can't launch multiproccessing.Process on methods

Changes by terry.h : -- nosy: +terry.h ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue11969] Can't launch multiproccessing.Process on methods

Changes by Petri Lehtinen : -- stage: test needed -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11969] Can't launch multiproccessing.Process on methods

Terry J. Reedy added the comment: After looking at the doc chapter, I get that 'if __name__' block is needed on Windows. OK. batch mode with if __name__ block: testmp.py - print('Top of Module') class C: def f(s): print('Method C.f') if __name__ == '__main__': print('Start of

[issue11969] Can't launch multiproccessing.Process on methods

R. David Murray added the comment: REPL is the Python interactive prompt in this case (REPL is Read Eval Print Loop). So Jesse is saying that using multiprocessing from the REPL (at least on Windows) isn't supported. This is because on Windows multiprocessing needs to re-import the main pro

[issue11969] Can't launch multiproccessing.Process on methods

Terry J. Reedy added the comment: Jesse, I do not understand your comment, including 'REPL' -- components: +Windows versions: +Python 3.2 -Python 3.4 ___ Python tracker ___

[issue11969] Can't launch multiproccessing.Process on methods

Ram Rachum added the comment: Thanks for the `-u` tip and the correction to the code, Petri. I removed my previous files since yours is the definite one. And yeah, it's a Windows issue. -- ___ Python tracker

[issue11969] Can't launch multiproccessing.Process on methods

Changes by Ram Rachum : Removed file: http://bugs.python.org/file22027/test.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue11969] Can't launch multiproccessing.Process on methods

Changes by Ram Rachum : Removed file: http://bugs.python.org/file22144/patch.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue11969] Can't launch multiproccessing.Process on methods

Petri Lehtinen added the comment: Actually, I only commented on the patch format and not on the actual contents of the patch, sorry :) Your test method missed the self parameter, and the test case needed to be added to the testcases_other list for the test to be actually run. I attached a co

[issue11969] Can't launch multiproccessing.Process on methods

Petri Lehtinen added the comment: Your patch is good in this case, as the person who applies the patch knows which file is affected. In the future, use diff -u original_file modified_file to get a unified diff. It's the "de facto" format for patches. -- nosy: +petri.lehtinen ___

[issue11969] Can't launch multiproccessing.Process on methods

Ram Rachum added the comment: Diff attached, is it good? I'm not very experienced with diffs, I usually work with pull requests. -- keywords: +patch Added file: http://bugs.python.org/file22144/patch.diff ___ Python tracker

[issue11969] Can't launch multiproccessing.Process on methods

Ezio Melotti added the comment: The test should be a diff against Lib/test/test_multiprocessing.py that adds a unit test. -- nosy: +ezio.melotti ___ Python tracker ___

[issue11969] Can't launch multiproccessing.Process on methods

Ram Rachum added the comment: Why is this still marked as "test needed"? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11969] Can't launch multiproccessing.Process on methods

Ram Rachum added the comment: Test attached. -- Added file: http://bugs.python.org/file22027/test.py ___ Python tracker ___ ___ Pytho

[issue11969] Can't launch multiproccessing.Process on methods

Jesse Noller added the comment: Do things like this in the REPL are known not to work. Things are not protected in the if __name__ block so we can import the script properly to run it. -- ___ Python tracker _

[issue11969] Can't launch multiproccessing.Process on methods

Changes by Terry J. Reedy : -- stage: -> test needed title: Can't launch Process on built-in static method -> Can't launch multiproccessing.Process on methods ___ Python tracker __