Lines Matching refs:doctests

145 examples of doctests in the standard Python test suite and libraries.
547    doctests expecting "little integer" output still work in these cases.  This
765 functions that run doctests, establishing different defaults.  In such cases,
886    is an advanced feature that allows parameterization of doctests.  For example, a
942    no doctests are found are excluded from consideration. The default is a backward
988 their doctests systematically.  Prior to Python 2.4, :mod:`doctest` had a barely
990 doctests from multiple modules. :class:`Tester` was feeble, and in practice most
995 test suites from modules and text files containing doctests.  To integrate with
1008 from text files and modules with doctests:
1077       The global ``__file__`` was added to the globals provided to doctests
1099    and runs each doctest in the module.  If any of the doctests fail, then the
1116    drop-in replacement) that is used to extract doctests from the module.
1159    This is a module-global setting, and affects all future doctests run by module
1362    drop-in replacement) that is used to extract doctests from docstrings.
1402       (recursively) be searched for doctests.
1616 * Several functions convert doctests to executable Python programs, which can be
1675      The ability to use :func:`pdb.set_trace` usefully inside doctests was added.
1677 Functions that convert doctests to Python code, and possibly run the synthesized
1722    object whose doctests are of interest.  Argument *name* is the name (within the
1723    module) of the object with the doctests of interest.  The result is a string,
1731    prints a script version of function :func:`f`'s docstring, with doctests
1739    Debug the doctests for an object.
1765    Debug the doctests in a string.