[Python-Dev] Beta version of the new devguide

Nick Coghlan ncoghlan at gmail.com
Mon Jan 24 16:33:04 CET 2011

On Mon, Jan 24, 2011 at 9:29 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Mon, 24 Jan 2011 20:33:07 +1000
> Nick Coghlan <ncoghlan at gmail.com> wrote:
>> On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon <brett at python.org> wrote:
>> >> In "Getting Set Up" it describes how to build a pydebug build. Is that
>> >> really necessary for those who plan only to contribute by working on
>> >> pure Python code?
>> >>
>> >
>> > Yes, there is actually a laundry list of reasons even people only
>> > working on the stdlib should use a pydebug build.
>> And one big reason why I don't unless I have a specific need to check
>> something with it - it makes the already quite long running time for
>> the full test suite take even longer :)
> Please try the -j option to regrtest.

While I must admit I'm still not in the habit of running tests in
parallel, that's a substantial speed improvement regardless of build
type, so a non-debug build is still noticeably faster.

release (with -j4): 2 min 25 sec (3 min wall clock time)
pydebug (with -j4): 4 min 43 sec (10 min wall clock time)

Given that I typically *don't* need the extra info from a debug build
to analyse problems and a full configure and rebuild cycle takes less
time than a single pydebug test run, I'll happily stick with the much
faster test execution that comes from using a release build.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list