[issue3598] multiprocessing.Pool windows/linux behaviour difference

Mark Summerfield <[EMAIL PROTECTED]> added the comment: On 2008-08-19, Antoine Pitrou wrote: > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > For what it's worth, this is documented in > http://docs.python.org/dev/library/multiprocessing.html#windows Ah yes, sorry I missed that.

[issue3598] multiprocessing.Pool windows/linux behaviour difference

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: For what it's worth, this is documented in http://docs.python.org/dev/library/multiprocessing.html#windows -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]>

[issue3598] multiprocessing.Pool windows/linux behaviour difference

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: There is a problem in your script. On Windows, the remote processes have to import the mtest module, in order to execute the get_size() function. This in turn calls the main() function, which creates a new pool of processes, etc... expo

[issue3598] multiprocessing.Pool windows/linux behaviour difference

New submission from Mark Summerfield <[EMAIL PROTECTED]>: When the attached program is run on Linux it runs "instantly" and outputs one line, e.g.: $ python3 mtest.py 100 files, 1702627142 bytes (The number of bytes will vary depending on the system.) When run on Windows XP there is no output