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 terry.reedy
Recipients benjamin.peterson, eric.araujo, ezio.melotti, mark.dickinson, terry.reedy
Date 2011-05-07.17:20:27
SpamBayes Score 3.463163e-10
Marked as misclassified No
Message-id <1304788828.3.0.829009675693.issue11963@psf.upfronthosting.co.za>
In-reply-to
Content
My title suggestion was meant to say "Yes, if you are willing to expand the scope of this issue and do more work, go ahead' ;-).

I have not looked at help(test), but it should be complete if it is not.
I was referring to the test module doc 25.5. Someone decided recently that test.support 25.6 should be complete, for the benefit of developers (like me) even though subject to change. Hence the recent patch. That chapter should probably start with a notice that these are private interfaces, subject to change, for testing of Python.

I'd like to see at least a listing and brief description of other stuff I should know about, perhaps in a new 25.6.2 section. An alternative would be something in the developer docs. Looking at the listing of /test is a bit confusing. I have pretty much ignored everything other than test_x (and regrtest.py), assuming that they were data files used by particular tests. Hence I was surprised by script_helper.py as an annex to support.py. Are there others (that are not single-test specific)? (I know, this should become another issue.)
History
Date User Action Args
2011-05-07 17:20:28terry.reedysetrecipients: + terry.reedy, mark.dickinson, benjamin.peterson, ezio.melotti, eric.araujo
2011-05-07 17:20:28terry.reedysetmessageid: <1304788828.3.0.829009675693.issue11963@psf.upfronthosting.co.za>
2011-05-07 17:20:27terry.reedylinkissue11963 messages
2011-05-07 17:20:27terry.reedycreate