[issue11389] unittest: no way to control verbosity of doctests from cmd

New submission from anatoly techtonik : I can't find a way to execute DocTests contained in a separate README.txt file using unittest.main() function. That doesn't allow to control verbosity for debugging. I am doing it this way in the tests.py import doctest import unittest if __name__ == '_

[issue11389] unittest: no way to control verbosity of doctests from cmd

Terry J. Reedy added the comment: The undocumented verbosity parameter? -- nosy: +michael.foord, terry.reedy ___ Python tracker ___ _

[issue11389] unittest: no way to control verbosity of doctests from cmd

Michael Foord added the comment: If the verbosity parameter isn't sufficient (which needs documenting but that is issue 11385) then it would need to be a feature request on DocFileSuite (part of doctest). -- ___ Python tracker

[issue11389] unittest: no way to control verbosity of doctests from cmd

anatoly techtonik added the comment: I need to execute doctests along with unit tests from test suite contained in tests.py file and control verbosity parameter in case something goes wrong. -- ___ Python tracker

[issue11389] unittest: no way to control verbosity of doctests from cmd

Michael Foord added the comment: Anatoly, does the verbosity parameter work for you? If not then any feature request / change needs to be for the DocFileSuite as the information is coming from there rather than unittest itself. -- assignee: docs@python -> versions: +Python 3.3 _

[issue11389] unittest: no way to control verbosity of doctests from cmd

Changes by Terry J. Reedy : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> TextTestRunner methods are not documented ___ Python tracker _

[issue11389] unittest: no way to control verbosity of doctests from cmd

Changes by Mark Lawrence : -- type: -> behavior versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker ___ ___