[issue20109] TestProgram is mentioned in the unittest docs but is not documented

Change by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

Change by Irit Katriel : -- keywords: +easy versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.3, Python 3.4 ___ Python tracker ___

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

Michael Foord added the comment: TestProgram is an abomination, but it has been publicly exposed in unittest since forever. -- ___ Python tracker ___ ___

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

Tamás Bence Gedai added the comment: I think TestProgram should be anonymous, all the work is done in its constructor. I don't see why would anyone would call its functions. I can update the docs if it's needed. -- nosy: +beng94 ___ Python tracker

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

Changes by Ezio Melotti : -- nosy: +ezio.melotti, michael.foord type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mail

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

New submission from R. David Murray: IMO, TestProgram should either be made anonymous in the docs ('main returns an object that has a results attribute...') or its external API should be formally documented. If results is the only external API other than its init (which is documented as unitt