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 nadeem.vawda
Recipients barry, brett.cannon, nadeem.vawda, ncoghlan, pitrou, rosslagerwall
Date 2011-03-23.20:55:16
SpamBayes Score 1.1210941e-06
Marked as misclassified No
Message-id <1300913718.48.0.273607011611.issue11651@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the actual times with -j0, I don't think there is any need to
keep quicktest - with the removal of the duplicate test, I can do a full
run in 3m16s (on a debug build; non-debug takes 1m54s), which seems plenty
fast enough.

One thing I noticed about the -j option is that it prevents test_curses from
running, since the child process actually running the test isn't connected
to a terminal. I don't know if this is an issue (the curses module doesn't
appear to be under active development), but I thought it was worth pointing
out.
History
Date User Action Args
2011-03-23 20:55:18nadeem.vawdasetrecipients: + nadeem.vawda, barry, brett.cannon, ncoghlan, pitrou, rosslagerwall
2011-03-23 20:55:18nadeem.vawdasetmessageid: <1300913718.48.0.273607011611.issue11651@psf.upfronthosting.co.za>
2011-03-23 20:55:17nadeem.vawdalinkissue11651 messages
2011-03-23 20:55:17nadeem.vawdacreate