This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, benjamin.peterson, collinwinter, nedds, pitrou
Date 2008-10-07.11:38:42
SpamBayes Score 4.4748103e-09
Marked as misclassified No
Message-id <1223379524.12.0.700209017883.issue3448@psf.upfronthosting.co.za>
In-reply-to
Content
I suggest that when using lib2to3 as a library, multiprocessing is not
enabled by default; there may be uses of the library that are
incompatible with multiprocessing.

It may be enabled by default when using it from the command line (or the
lib2to3.main module). But which default number of processes would this use?

Concerning the patch itself: 
- the line "from processing import Process" seems suspect.
- Did you consider using something as simple as:
    pool = multiprocessing.Pool(self.options.num_processes)
    pool.map(self.refactor_file, fullnames)
It should do all the job: start processes, queue tasks, wait for results.
History
Date User Action Args
2008-10-07 11:38:44amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, collinwinter, pitrou, benjamin.peterson, nedds
2008-10-07 11:38:44amaury.forgeotdarcsetmessageid: <1223379524.12.0.700209017883.issue3448@psf.upfronthosting.co.za>
2008-10-07 11:38:43amaury.forgeotdarclinkissue3448 messages
2008-10-07 11:38:42amaury.forgeotdarccreate