Message 74145 - Python tracker

➜

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	nedds
Recipients	benjamin.peterson, collinwinter, nedds
Date	2008-10-01.20:43:57
SpamBayes Score	5.7442076e-06
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
The currently attached patch works in Python2.5 not Python2.6, so I will update it for 2.6 when I get the chance. But as it is currently written, the default behavior is not multiprocess. Instead, if you want multiprocess, you specify how many processes you want when you run 2to3 from the command line. And as long as you've got multiple files to run 2to3 on and multiple cores, doing multiprocess 2to3 is significantly faster.

The currently attached patch works in Python2.5 not Python2.6, so I will
update it for 2.6 when I get the chance. But as it is currently written,
the default behavior is not multiprocess. Instead, if you want
multiprocess, you specify how many processes you want when you run 2to3
from the command line. And as long as you've got multiple files to run
2to3 on and multiple cores, doing multiprocess 2to3 is significantly faster.

History
Date	User	Action	Args
2008-10-01 20:43:58	nedds	set	recipients: + nedds, collinwinter, benjamin.peterson
2008-10-01 20:43:58	nedds	set	messageid: <[email protected]>
2008-10-01 20:43:58	nedds	link	issue3448 messages
2008-10-01 20:43:57	nedds	create