@@ -321,6 +321,10 @@ but doctest isn't trying to do an exact emulation of any specific Python shell.
321321 NO!!!
322322 >>>
323323
324+ .. index ::
325+ single: >>>; interpreter prompt
326+ single: ...; interpreter prompt
327+
324328Any expected output must immediately follow the final ``'>>> ' `` or ``'... ' ``
325329line containing the code, and the expected output (if any) extends to the next
326330``'>>> ' `` or all-whitespace line.
@@ -481,6 +485,8 @@ Some details you should read once, but won't need to remember:
481485 to test a :exc: `SyntaxError ` that omits the traceback header, you will need to
482486 manually add the traceback header line to your test example.
483487
488+ .. index :: single: ^; caret
489+
484490* For some :exc: `SyntaxError `\ s, Python displays the character position of the
485491 syntax error, using a ``^ `` marker::
486492
@@ -532,6 +538,7 @@ doctest decides whether actual output matches an example's expected output:
532538 option will probably go away, but not for several years.
533539
534540
541+ .. index :: single: <BLANKLINE>
535542.. data :: DONT_ACCEPT_BLANKLINE
536543
537544 By default, if an expected output block contains a line containing only the
@@ -551,6 +558,7 @@ doctest decides whether actual output matches an example's expected output:
551558 your source.
552559
553560
561+ .. index :: single: ...; in doctests
554562.. data :: ELLIPSIS
555563
556564 When specified, an ellipsis marker (``... ``) in the expected output can match
@@ -686,6 +694,10 @@ useful unless you intend to extend :mod:`doctest` internals via subclassing:
686694 MY_FLAG = register_optionflag('MY_FLAG')
687695
688696
697+ .. index ::
698+ single: #; in doctests
699+ single: +; in doctests
700+ single: -; in doctests
689701.. _doctest-directives :
690702
691703Directives
0 commit comments