The biggest problem with make test is it is not exactly the same as the script (e.g., no automatic -j usage). It also is not cross-platform since Windows dev's are left out without installing cygwin. And we can't simply use -m test as that leaves out flags passed to the interpreter. On Mar 1, 2011 5:45 AM, "Antoine Pitrou" <solip...@pitrou.net> wrote: > On Tue, 1 Mar 2011 23:36:38 +1000 > Nick Coghlan <ncogh...@gmail.com> wrote: >> On Tue, Mar 1, 2011 at 8:03 AM, brett.cannon <python-check...@python.org> wrote: >> > brett.cannon pushed 3e5a61adb41d to devinabox: >> > >> > http://hg.python.org/devinabox/rev/3e5a61adb41d >> > changeset: 8:3e5a61adb41d >> > user: Brett Cannon <br...@python.org> >> > date: Fri Feb 25 17:35:37 2011 -0800 >> > summary: >> > Add a Python script which will run the test suite in the most rigorous way possible. >> >> Is there any particular reason not to stick this in the main >> repository somewhere, so it is available in all working copies, not >> just devinabox? > > We already have "make test" and "make buildbottest" in addition to > "./python -m test". I think another subtly different way of running the > tests would be a nuisance. > > cheers > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
