-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestProgram is mentioned in the unittest docs but is not documented #64308
Comments
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 unittest.main), then I would suggest the former. In either case exactly what 'results' contains should be clarified. |
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. |
TestProgram is an abomination, but it has been publicly exposed in unittest since forever. |
I'm working on this during EuroPython 2024 sprint. I'll anonymize |
…21675) (cherry picked from commit f6f4022) Co-authored-by: Jan Musílek <[email protected]>
…21675) (cherry picked from commit f6f4022) Co-authored-by: Jan Musílek <[email protected]>
GH-121742) (cherry picked from commit f6f4022) Co-authored-by: Jan Musílek <[email protected]>
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
Linked PRs
The text was updated successfully, but these errors were encountered: