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 rhettinger
Recipients brett.cannon, ezio.melotti, michael.foord, python-dev, r.david.murray, rhettinger, serhiy.storchaka, terry.reedy, zach.ware
Date 2014-06-19.20:13:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403208792.91.0.900152571564.issue21741@psf.upfronthosting.co.za>
In-reply-to
Content
>  My ultimate goal along those lines is to eradicate
> support.run_unittest, and this is a step in that direction.
>
>I think there's enough support here to skip python-dev :).

Not really.  There is support here for using unittest.main() whereever it fits and cleans-up the code.  That is not the same as saying we can eliminate support.run_unittest().  That is likely a more thorny issue and may affect users outside the standard library.

> @Raymond: May I ask why you removed 3.4 from versions?

Because we don't backport this sort of change.  The ship for version 3.4 has sailed.  There's no point in rewriting history for something that isn't a bug fix, documentation fix, or performance regression.  Also, who knows who is already relying on the current setup and would have their code broken in the next micro-release.   (Second law of time travel: the past is infinitely fragile and the future is infinitely mallable)
History
Date User Action Args
2014-06-19 20:13:12rhettingersetrecipients: + rhettinger, brett.cannon, terry.reedy, ezio.melotti, r.david.murray, michael.foord, python-dev, zach.ware, serhiy.storchaka
2014-06-19 20:13:12rhettingersetmessageid: <1403208792.91.0.900152571564.issue21741@psf.upfronthosting.co.za>
2014-06-19 20:13:12rhettingerlinkissue21741 messages
2014-06-19 20:13:12rhettingercreate