[issue10849] Backport test/__main__

Antoine Pitrou added the comment: A backport would be more attractive if the Windows issue was fixed first... (and I don't care about the "policy" here: anything which makes testing easier is good IMO, and we have routinely backported tests as mentioned by someone else) -- nosy: +pitr

[issue10849] Backport test/__main__

Georg Brandl added the comment: Okay, that's reasonable enough. Closing (or shall we wait for the majority to consent first?) -- resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue10849] Backport test/__main__

Martin v. Löwis added the comment: I'm with Raymond here (probably not surprisingly): -1 on backporting new features into 2.7. This really is foremost about having policies and sticking to them; special cases aren't special enough to break the rules. Personally, I haven't arrived yet at usin

[issue10849] Backport test/__main__

Georg Brandl added the comment: > The possible downside, as with any new feature, is that code using the > new feature will not run on on previous micro (x.y.z) releases. That's absolutely no downside: I daresay 99% of test runs by developers are done at the branch head, not some released vers

[issue10849] Backport test/__main__

Terry J. Reedy added the comment: The possible downside, as with any new feature, is that code using the new feature will not run on on previous micro (x.y.z) releases. In this case, one can run the tests using the new feature. >>> from test import __main__ == CPython 3.2b2 (r32b2:87398, Dec

[issue10849] Backport test/__main__

Benjamin Peterson added the comment: 2011/1/7 Raymond Hettinger : > > Raymond Hettinger added the comment: > > His +0 isn't a decision.  I would like Martin, the longest term active > developer, to make the call about waiving the policy of not backporting > features (especially when the only

[issue10849] Backport test/__main__

Changes by Georg Brandl : -- nosy: -georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10849] Backport test/__main__

Georg Brandl added the comment: Oh, sure. I misinterpreted your comment. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue10849] Backport test/__main__

Raymond Hettinger added the comment: His +0 isn't a decision. I would like Martin, the longest term active developer, to make the call about waiving the policy of not backporting features (especially when the only purported benefit saving a couple of core devs from spelling out the path name

[issue10849] Backport test/__main__

Georg Brandl added the comment: I thought Benjamin was still RM for 2.7 and 3.1? -- assignee: loewis -> benjamin.peterson nosy: +georg.brandl ___ Python tracker ___

[issue10849] Backport test/__main__

Raymond Hettinger added the comment: 2.6 is right out. Martin, would you please decide on whether this should be backported to 2.7 and 3.1? IMO, the rationale is flimsy (its not hard to run the test suite in *any* version) and it goes against our usual policy; however, it is also a trivial

[issue10849] Backport test/__main__

Benjamin Peterson added the comment: +0. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10849] Backport test/__main__

Changes by Georg Brandl : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mail

[issue10849] Backport test/__main__

Éric Araujo added the comment: FWIW, I’ve already been caught by “./python -m test” not working with 3.1 and 2.7 when doing backports and using my shell history functionality. I share Alexander’s viewpoint that adding test.__main__ is a core dev-specific convenience that should not count as

[issue10849] Backport test/__main__

Alexander Belopolsky added the comment: > -0 we don't backport new features New tests are routinely backported when they accompany bug fixes, so new features under Lib/test are probably a fair game. Given that this feature is implemented entirely in a file that is not used for any other purp

[issue10849] Backport test/__main__

Raymond Hettinger added the comment: -0 we don't backport new features -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-li

[issue10849] Backport test/__main__

Changes by Sandro Tosi : -- nosy: +sandro.tosi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10849] Backport test/__main__

Changes by Alexander Belopolsky : -- nosy: +michael.foord ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue10849] Backport test/__main__

New submission from Alexander Belopolsky : It is much easier to remember and to type -m test instead of -m test.regrtest, but the usefulness of this feature is limited by the fact that it only works with the latest version. Since this does not require any user-visible changes, I think it shoul