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 dholth
Recipients dholth
Date 2012-10-01.20:46:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349124414.14.0.0730954283721.issue16104@psf.upfronthosting.co.za>
In-reply-to
Content
compileall would benefit approximately linearly from additional CPU cores.  There should be an option.

The noisy output would have to change. Right now it prints "compiling" and then "done" synchronously with doing the actual work.
History
Date User Action Args
2012-10-01 20:46:54dholthsetrecipients: + dholth
2012-10-01 20:46:54dholthsetmessageid: <1349124414.14.0.0730954283721.issue16104@psf.upfronthosting.co.za>
2012-10-01 20:46:54dholthlinkissue16104 messages
2012-10-01 20:46:53dholthcreate