Lines Matching refs:docstring

202 were a single giant docstring; the file doesn't need to contain a Python
277 The module docstring, and all function, class and method docstrings are
353   other reason use a backslash, you should use a raw docstring, which will
357      ...     r'''Backslashes in a raw docstring: m\n'''
359      Backslashes in a raw docstring: m\n
366      ...     '''Backslashes in a raw docstring: m\\n'''
368      Backslashes in a raw docstring: m\n
386 By default, each time :mod:`doctest` finds a docstring to test, it uses a
391 in the docstring being run. Examples cannot see names defined in other
1151   from a single docstring or text file.
1157   :class:`DocTestParser` to create a :class:`DocTest` from every docstring that
1161   as an object's docstring).
1188 .. class:: DocTest(examples, globs, name, filename, lineno, docstring)
1232    .. attribute:: docstring
1309    a given object, from its docstring and the docstrings of its contained objects.
1332       docstring, or by any of its contained objects' docstrings.
1576   contains just this module docstring::
1666    containing the object's docstring converted to a Python script, as described for
1673    prints a script version of function :func:`f`'s docstring, with doctests
1683    docstring is written to a temporary file, and then that file is run under the
1714 the source code, and especially :class:`DebugRunner`'s docstring (which is a
1800 When writing a docstring, choose docstring examples with care. There's an art to