[issue9255] document that the 'test' package is for core developers only

Terry J. Reedy added the comment: 3.2: r83072 3.1: r83076 2.7: r83077 -- nosy: +tjreedy ___ Python tracker ___ ___ Python-bugs-list ma

[issue9255] document that the 'test' package is for core developers only

Éric Araujo added the comment: Brett, could you add “r” or “rev ” before revision numbers in the future? It’s Roundup implicit markup to make a link to a revision. (Evil but handy.) Thanks in advance :) -- nosy: +merwok stage: needs patch -> committed/rejected ___

[issue9255] document that the 'test' package is for core developers only

Brett Cannon added the comment: 3.2: 83072 3.1: 83076 2.7: 83077 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue9255] document that the 'test' package is for core developers only

R. David Murray added the comment: "Use it at your own risk" is always an option. Brett is saying that test.support docs need to make it clear that anyone using it is doing so at their own risk: it is for core development only and so we might change anything at any time without considering b

[issue9255] document that the 'test' package is for core developers only

Alexander Belopolsky added the comment: Issue 8273 is in some sense the opposite of this - it calls for blessing of everything in in test.support while this issue calls for wholesale "unblessing". I don't think either approach is right. While users should definitely never import test_* modu

[issue9255] document that the 'test' package is for core developers only

R. David Murray added the comment: Alexander: issue8273 addresses this, but I don't think Brett's doc change should be held up pending the resolution of that issue. Also, the entire set of test.support documentation should move to a set of 'developer' docs (which I think Brett plans to write

[issue9255] document that the 'test' package is for core developers only

Alexander Belopolsky added the comment: It would be nice if at the same time the facilities available in test.support and test.regrtest were reviewed and some promoted to user facing unittest package. They can even be placed in unittest.support and unittest.regrtest modules for easy discover

[issue9255] document that the 'test' package is for core developers only

New submission from Brett Cannon : The documentation for the 'test' package should specify that the things that are documented are really meant for people contributing to Python and not for personal use. This will help lead to people no longer using the package outside of Python itself and eve