# Copyright (C) 2001-2020, Python Software Foundation

# This file is distributed under the same license as the Python package.

# Maintained by the python-doc-es workteam.

# docs-es@python.org /

# https://mail.python.org/mailman3/lists/docs-es.python.org/

# Check https://github.com/PyCampES/python-docs-es/blob/3.8/TRANSLATORS to

# get the list of volunteers

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.8\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2020-05-05 12:54+0200\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: python-doc-es\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=utf-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Generated-By: Babel 2.8.0\n"

#: ../Doc/library/doctest.rst:2

msgid ":mod:`doctest` --- Test interactive Python examples"

msgstr ""

#: ../Doc/library/doctest.rst:12

msgid "**Source code:** :source:`Lib/doctest.py`"

msgstr ""

#: ../Doc/library/doctest.rst:16

msgid ""

"The :mod:`doctest` module searches for pieces of text that look like "

"interactive Python sessions, and then executes those sessions to verify that "

"they work exactly as shown. There are several common ways to use doctest:"

msgstr ""

#: ../Doc/library/doctest.rst:20

msgid ""

"To check that a module's docstrings are up-to-date by verifying that all "

"interactive examples still work as documented."

msgstr ""

#: ../Doc/library/doctest.rst:23

msgid ""

"To perform regression testing by verifying that interactive examples from a "

"test file or a test object work as expected."

msgstr ""

#: ../Doc/library/doctest.rst:26

msgid ""

"To write tutorial documentation for a package, liberally illustrated with "

"input-output examples. Depending on whether the examples or the expository "

"text are emphasized, this has the flavor of \"literate testing\" or "

"\"executable documentation\"."

msgstr ""

#: ../Doc/library/doctest.rst:31

msgid "Here's a complete but small example module::"

msgstr ""

#: ../Doc/library/doctest.rst:88

msgid ""

"If you run :file:`example.py` directly from the command line, :mod:`doctest` "

"works its magic:"

msgstr ""

#: ../Doc/library/doctest.rst:96

msgid ""

"There's no output! That's normal, and it means all the examples worked. "

"Pass ``-v`` to the script, and :mod:`doctest` prints a detailed log of what "

"it's trying, and prints a summary at the end:"

msgstr ""

#: ../Doc/library/doctest.rst:114

msgid "And so on, eventually ending with:"

msgstr ""

#: ../Doc/library/doctest.rst:133

msgid ""

"That's all you need to know to start making productive use of :mod:"

"`doctest`! Jump in. The following sections provide full details. Note that "

"there are many examples of doctests in the standard Python test suite and "

"libraries. Especially useful examples can be found in the standard test "

"file :file:`Lib/test/test_doctest.py`."

msgstr ""

#: ../Doc/library/doctest.rst:143

msgid "Simple Usage: Checking Examples in Docstrings"

msgstr ""

#: ../Doc/library/doctest.rst:145

msgid ""

"The simplest way to start using doctest (but not necessarily the way you'll "

"continue to do it) is to end each module :mod:`M` with::"

msgstr ""

#: ../Doc/library/doctest.rst:152

msgid ":mod:`doctest` then examines docstrings in module :mod:`M`."

msgstr ""

#: ../Doc/library/doctest.rst:154

msgid ""

"Running the module as a script causes the examples in the docstrings to get "

"executed and verified::"

msgstr ""

#: ../Doc/library/doctest.rst:159

msgid ""

"This won't display anything unless an example fails, in which case the "

"failing example(s) and the cause(s) of the failure(s) are printed to stdout, "

"and the final line of output is ``***Test Failed*** N failures.``, where *N* "

"is the number of examples that failed."

msgstr ""

#: ../Doc/library/doctest.rst:164

msgid "Run it with the ``-v`` switch instead::"

msgstr ""

#: ../Doc/library/doctest.rst:168

msgid ""

"and a detailed report of all examples tried is printed to standard output, "

"along with assorted summaries at the end."

msgstr ""

#: ../Doc/library/doctest.rst:171

msgid ""

"You can force verbose mode by passing ``verbose=True`` to :func:`testmod`, "

"or prohibit it by passing ``verbose=False``. In either of those cases, "

"``sys.argv`` is not examined by :func:`testmod` (so passing ``-v`` or not "

"has no effect)."

msgstr ""

#: ../Doc/library/doctest.rst:176

msgid ""

"There is also a command line shortcut for running :func:`testmod`. You can "

"instruct the Python interpreter to run the doctest module directly from the "

"standard library and pass the module name(s) on the command line::"

msgstr ""

#: ../Doc/library/doctest.rst:182

msgid ""

"This will import :file:`example.py` as a standalone module and run :func:"

"`testmod` on it. Note that this may not work correctly if the file is part "

"of a package and imports other submodules from that package."

msgstr ""

#: ../Doc/library/doctest.rst:186

msgid ""

"For more information on :func:`testmod`, see section :ref:`doctest-basic-"

"api`."

msgstr ""

#: ../Doc/library/doctest.rst:192

msgid "Simple Usage: Checking Examples in a Text File"

msgstr ""

#: ../Doc/library/doctest.rst:194

msgid ""

"Another simple application of doctest is testing interactive examples in a "

"text file. This can be done with the :func:`testfile` function::"

msgstr ""

#: ../Doc/library/doctest.rst:200

msgid ""

"That short script executes and verifies any interactive Python examples "

"contained in the file :file:`example.txt`. The file content is treated as "

"if it were a single giant docstring; the file doesn't need to contain a "

"Python program! For example, perhaps :file:`example.txt` contains this:"

msgstr ""

#: ../Doc/library/doctest.rst:223

msgid ""

"Running ``doctest.testfile(\"example.txt\")`` then finds the error in this "

"documentation::"

msgstr ""

#: ../Doc/library/doctest.rst:234

msgid ""

"As with :func:`testmod`, :func:`testfile` won't display anything unless an "

"example fails. If an example does fail, then the failing example(s) and the "

"cause(s) of the failure(s) are printed to stdout, using the same format as :"

"func:`testmod`."

msgstr ""

#: ../Doc/library/doctest.rst:239

msgid ""

"By default, :func:`testfile` looks for files in the calling module's "

"directory. See section :ref:`doctest-basic-api` for a description of the "

"optional arguments that can be used to tell it to look for files in other "

"locations."

msgstr ""

#: ../Doc/library/doctest.rst:243

msgid ""

"Like :func:`testmod`, :func:`testfile`'s verbosity can be set with the ``-"

"v`` command-line switch or with the optional keyword argument *verbose*."

msgstr ""

#: ../Doc/library/doctest.rst:247

msgid ""

"There is also a command line shortcut for running :func:`testfile`. You can "

"instruct the Python interpreter to run the doctest module directly from the "

"standard library and pass the file name(s) on the command line::"

msgstr ""

#: ../Doc/library/doctest.rst:253

msgid ""

"Because the file name does not end with :file:`.py`, :mod:`doctest` infers "

"that it must be run with :func:`testfile`, not :func:`testmod`."

msgstr ""

#: ../Doc/library/doctest.rst:256

msgid ""

"For more information on :func:`testfile`, see section :ref:`doctest-basic-"

"api`."

msgstr ""

#: ../Doc/library/doctest.rst:262

msgid "How It Works"

msgstr ""

#: ../Doc/library/doctest.rst:264

msgid ""

"This section examines in detail how doctest works: which docstrings it looks "

"at, how it finds interactive examples, what execution context it uses, how "

"it handles exceptions, and how option flags can be used to control its "

"behavior. This is the information that you need to know to write doctest "

"examples; for information about actually running doctest on these examples, "

"see the following sections."

msgstr ""

#: ../Doc/library/doctest.rst:275

msgid "Which Docstrings Are Examined?"

msgstr ""

#: ../Doc/library/doctest.rst:277

msgid ""

"The module docstring, and all function, class and method docstrings are "

"searched. Objects imported into the module are not searched."

msgstr ""

#: ../Doc/library/doctest.rst:280

msgid ""

"In addition, if ``M.__test__`` exists and \"is true\", it must be a dict, "

"and each entry maps a (string) name to a function object, class object, or "

"string. Function and class object docstrings found from ``M.__test__`` are "

"searched, and strings are treated as if they were docstrings. In output, a "

"key ``K`` in ``M.__test__`` appears with name ::"

msgstr ""

#: ../Doc/library/doctest.rst:288

msgid ""

"Any classes found are recursively searched similarly, to test docstrings in "

"their contained methods and nested classes."

msgstr ""

#: ../Doc/library/doctest.rst:299

msgid "How are Docstring Examples Recognized?"

msgstr ""

#: ../Doc/library/doctest.rst:301

msgid ""

"In most cases a copy-and-paste of an interactive console session works fine, "

"but doctest isn't trying to do an exact emulation of any specific Python "

"shell."

msgstr ""

#: ../Doc/library/doctest.rst:326

msgid ""

"Any expected output must immediately follow the final ``'>>> '`` or ``'... "

"'`` line containing the code, and the expected output (if any) extends to "

"the next ``'>>> '`` or all-whitespace line."

msgstr ""

#: ../Doc/library/doctest.rst:330

msgid "The fine print:"

msgstr ""

#: ../Doc/library/doctest.rst:332

msgid ""

"Expected output cannot contain an all-whitespace line, since such a line is "

"taken to signal the end of expected output. If expected output does contain "

"a blank line, put ``<BLANKLINE>`` in your doctest example each place a blank "

"line is expected."

msgstr ""

#: ../Doc/library/doctest.rst:337

msgid ""

"All hard tab characters are expanded to spaces, using 8-column tab stops. "

"Tabs in output generated by the tested code are not modified. Because any "

"hard tabs in the sample output *are* expanded, this means that if the code "

"output includes hard tabs, the only way the doctest can pass is if the :"

"const:`NORMALIZE_WHITESPACE` option or :ref:`directive <doctest-directives>` "

"is in effect. Alternatively, the test can be rewritten to capture the output "

"and compare it to an expected value as part of the test. This handling of "

"tabs in the source was arrived at through trial and error, and has proven to "

"be the least error prone way of handling them. It is possible to use a "

"different algorithm for handling tabs by writing a custom :class:"

"`DocTestParser` class."

msgstr ""

#: ../Doc/library/doctest.rst:349

msgid ""

"Output to stdout is captured, but not output to stderr (exception tracebacks "

"are captured via a different means)."

msgstr ""

#: ../Doc/library/doctest.rst:352

msgid ""

"If you continue a line via backslashing in an interactive session, or for "

"any other reason use a backslash, you should use a raw docstring, which will "

"preserve your backslashes exactly as you type them::"

msgstr ""

#: ../Doc/library/doctest.rst:361

msgid ""

"Otherwise, the backslash will be interpreted as part of the string. For "

"example, the ``\\n`` above would be interpreted as a newline character. "

"Alternatively, you can double each backslash in the doctest version (and not "

"use a raw string)::"

msgstr ""

#: ../Doc/library/doctest.rst:370

msgid "The starting column doesn't matter::"

msgstr ""

#: ../Doc/library/doctest.rst:377

msgid ""

"and as many leading whitespace characters are stripped from the expected "

"output as appeared in the initial ``'>>> '`` line that started the example."

msgstr ""

#: ../Doc/library/doctest.rst:384

msgid "What's the Execution Context?"

msgstr ""

#: ../Doc/library/doctest.rst:386

msgid ""

"By default, each time :mod:`doctest` finds a docstring to test, it uses a "

"*shallow copy* of :mod:`M`'s globals, so that running tests doesn't change "

"the module's real globals, and so that one test in :mod:`M` can't leave "

"behind crumbs that accidentally allow another test to work. This means "

"examples can freely use any names defined at top-level in :mod:`M`, and "

"names defined earlier in the docstring being run. Examples cannot see names "

"defined in other docstrings."

msgstr ""

#: ../Doc/library/doctest.rst:394

msgid ""

"You can force use of your own dict as the execution context by passing "

"``globs=your_dict`` to :func:`testmod` or :func:`testfile` instead."

msgstr ""

#: ../Doc/library/doctest.rst:401

msgid "What About Exceptions?"

msgstr ""

#: ../Doc/library/doctest.rst:403

msgid ""

"No problem, provided that the traceback is the only output produced by the "

"example: just paste in the traceback. [#]_ Since tracebacks contain details "

"that are likely to change rapidly (for example, exact file paths and line "

"numbers), this is one case where doctest works hard to be flexible in what "

"it accepts."

msgstr ""

#: ../Doc/library/doctest.rst:409

msgid "Simple example::"

msgstr ""

#: ../Doc/library/doctest.rst:416

msgid ""

"That doctest succeeds if :exc:`ValueError` is raised, with the ``list."

"remove(x): x not in list`` detail as shown."

msgstr ""

#: ../Doc/library/doctest.rst:419

msgid ""

"The expected output for an exception must start with a traceback header, "

"which may be either of the following two lines, indented the same as the "

"first line of the example::"

msgstr ""

#: ../Doc/library/doctest.rst:426

msgid ""

"The traceback header is followed by an optional traceback stack, whose "

"contents are ignored by doctest. The traceback stack is typically omitted, "

"or copied verbatim from an interactive session."

msgstr ""

#: ../Doc/library/doctest.rst:430

msgid ""

"The traceback stack is followed by the most interesting part: the line(s) "

"containing the exception type and detail. This is usually the last line of "

"a traceback, but can extend across multiple lines if the exception has a "

"multi-line detail::"

msgstr ""

#: ../Doc/library/doctest.rst:442

msgid ""

"The last three lines (starting with :exc:`ValueError`) are compared against "

"the exception's type and detail, and the rest are ignored."

msgstr ""

#: ../Doc/library/doctest.rst:445

msgid ""

"Best practice is to omit the traceback stack, unless it adds significant "

"documentation value to the example. So the last example is probably better "

"as::"

msgstr ""

#: ../Doc/library/doctest.rst:455

msgid ""

"Note that tracebacks are treated very specially. In particular, in the "

"rewritten example, the use of ``...`` is independent of doctest's :const:"

"`ELLIPSIS` option. The ellipsis in that example could be left out, or could "

"just as well be three (or three hundred) commas or digits, or an indented "

"transcript of a Monty Python skit."

msgstr ""

#: ../Doc/library/doctest.rst:461

msgid "Some details you should read once, but won't need to remember:"

msgstr ""

#: ../Doc/library/doctest.rst:463

msgid ""

"Doctest can't guess whether your expected output came from an exception "

"traceback or from ordinary printing. So, e.g., an example that expects "

"``ValueError: 42 is prime`` will pass whether :exc:`ValueError` is actually "

"raised or if the example merely prints that traceback text. In practice, "

"ordinary output rarely begins with a traceback header line, so this doesn't "

"create real problems."

msgstr ""

#: ../Doc/library/doctest.rst:470

msgid ""

"Each line of the traceback stack (if present) must be indented further than "

"the first line of the example, *or* start with a non-alphanumeric character. "

"The first line following the traceback header indented the same and starting "

"with an alphanumeric is taken to be the start of the exception detail. Of "

"course this does the right thing for genuine tracebacks."

msgstr ""

#: ../Doc/library/doctest.rst:476

msgid ""

"When the :const:`IGNORE_EXCEPTION_DETAIL` doctest option is specified, "

"everything following the leftmost colon and any module information in the "

"exception name is ignored."

msgstr ""

#: ../Doc/library/doctest.rst:480

msgid ""

"The interactive shell omits the traceback header line for some :exc:"

"`SyntaxError`\\ s. But doctest uses the traceback header line to "

"distinguish exceptions from non-exceptions. So in the rare case where you "

"need to test a :exc:`SyntaxError` that omits the traceback header, you will "

"need to manually add the traceback header line to your test example."

msgstr ""

#: ../Doc/library/doctest.rst:488

msgid ""

"For some :exc:`SyntaxError`\\ s, Python displays the character position of "

"the syntax error, using a ``^`` marker::"

msgstr ""

#: ../Doc/library/doctest.rst:497

msgid ""

"Since the lines showing the position of the error come before the exception "

"type and detail, they are not checked by doctest. For example, the "

"following test would pass, even though it puts the ``^`` marker in the wrong "

"location::"

msgstr ""

#: ../Doc/library/doctest.rst:513

msgid "Option Flags"

msgstr ""

#: ../Doc/library/doctest.rst:515

msgid ""

"A number of option flags control various aspects of doctest's behavior. "

"Symbolic names for the flags are supplied as module constants, which can be :"

"ref:`bitwise ORed <bitwise>` together and passed to various functions. The "

"names can also be used in :ref:`doctest directives <doctest-directives>`, "

"and may be passed to the doctest command line interface via the ``-o`` "

"option."

msgstr ""

#: ../Doc/library/doctest.rst:521

msgid "The ``-o`` command line option."

msgstr ""

#: ../Doc/library/doctest.rst:524

msgid ""

"The first group of options define test semantics, controlling aspects of how "

"doctest decides whether actual output matches an example's expected output:"

msgstr ""

#: ../Doc/library/doctest.rst:530

msgid ""

"By default, if an expected output block contains just ``1``, an actual "

"output block containing just ``1`` or just ``True`` is considered to be a "

"match, and similarly for ``0`` versus ``False``. When :const:"

"`DONT_ACCEPT_TRUE_FOR_1` is specified, neither substitution is allowed. The "

"default behavior caters to that Python changed the return type of many "

"functions from integer to boolean; doctests expecting \"little integer\" "

"output still work in these cases. This option will probably go away, but "

"not for several years."

msgstr ""

#: ../Doc/library/doctest.rst:542

msgid ""

"By default, if an expected output block contains a line containing only the "

"string ``<BLANKLINE>``, then that line will match a blank line in the actual "

"output. Because a genuinely blank line delimits the expected output, this "

"is the only way to communicate that a blank line is expected. When :const:"

"`DONT_ACCEPT_BLANKLINE` is specified, this substitution is not allowed."

msgstr ""

#: ../Doc/library/doctest.rst:551

msgid ""

"When specified, all sequences of whitespace (blanks and newlines) are "

"treated as equal. Any sequence of whitespace within the expected output "

"will match any sequence of whitespace within the actual output. By default, "

"whitespace must match exactly. :const:`NORMALIZE_WHITESPACE` is especially "

"useful when a line of expected output is very long, and you want to wrap it "

"across multiple lines in your source."

msgstr ""

#: ../Doc/library/doctest.rst:562

msgid ""

"When specified, an ellipsis marker (``...``) in the expected output can "

"match any substring in the actual output. This includes substrings that "

"span line boundaries, and empty substrings, so it's best to keep usage of "

"this simple. Complicated uses can lead to the same kinds of \"oops, it "

"matched too much!\" surprises that ``.*`` is prone to in regular expressions."

msgstr ""

#: ../Doc/library/doctest.rst:571

msgid ""

"When specified, an example that expects an exception passes if an exception "

"of the expected type is raised, even if the exception detail does not "

"match. For example, an example expecting ``ValueError: 42`` will pass if "

"the actual exception raised is ``ValueError: 3*14``, but will fail, e.g., "

"if :exc:`TypeError` is raised."

msgstr ""

#: ../Doc/library/doctest.rst:577

msgid ""

"It will also ignore the module name used in Python 3 doctest reports. Hence "

"both of these variations will work with the flag specified, regardless of "

"whether the test is run under Python 2.7 or Python 3.2 (or later versions)::"

msgstr ""

#: ../Doc/library/doctest.rst:589

msgid ""

"Note that :const:`ELLIPSIS` can also be used to ignore the details of the "

"exception message, but such a test may still fail based on whether or not "

"the module details are printed as part of the exception name. Using :const:"

"`IGNORE_EXCEPTION_DETAIL` and the details from Python 2.3 is also the only "

"clear way to write a doctest that doesn't care about the exception detail "

"yet continues to pass under Python 2.3 or earlier (those releases do not "

"support :ref:`doctest directives <doctest-directives>` and ignore them as "

"irrelevant comments). For example::"

msgstr ""

#: ../Doc/library/doctest.rst:603

msgid ""

"passes under Python 2.3 and later Python versions with the flag specified, "

"even though the detail changed in Python 2.4 to say \"does not\" instead of "

"\"doesn't\"."

msgstr ""

#: ../Doc/library/doctest.rst:607

msgid ""

":const:`IGNORE_EXCEPTION_DETAIL` now also ignores any information relating "

"to the module containing the exception under test."

msgstr ""

#: ../Doc/library/doctest.rst:614

msgid ""

"When specified, do not run the example at all. This can be useful in "

"contexts where doctest examples serve as both documentation and test cases, "

"and an example should be included for documentation purposes, but should not "

"be checked. E.g., the example's output might be random; or the example "

"might depend on resources which would be unavailable to the test driver."

msgstr ""

#: ../Doc/library/doctest.rst:620

msgid ""

"The SKIP flag can also be used for temporarily \"commenting out\" examples."

msgstr ""

#: ../Doc/library/doctest.rst:625

msgid "A bitmask or'ing together all the comparison flags above."

msgstr ""

#: ../Doc/library/doctest.rst:627

msgid "The second group of options controls how test failures are reported:"

msgstr ""

#: ../Doc/library/doctest.rst:632

msgid ""

"When specified, failures that involve multi-line expected and actual outputs "

"are displayed using a unified diff."

msgstr ""

#: ../Doc/library/doctest.rst:638

msgid ""

"When specified, failures that involve multi-line expected and actual outputs "

"will be displayed using a context diff."

msgstr ""

#: ../Doc/library/doctest.rst:644

msgid ""

"When specified, differences are computed by ``difflib.Differ``, using the "

"same algorithm as the popular :file:`ndiff.py` utility. This is the only "

"method that marks differences within lines as well as across lines. For "

"example, if a line of expected output contains digit ``1`` where actual "

"output contains letter ``l``, a line is inserted with a caret marking the "

"mismatching column positions."

msgstr ""

#: ../Doc/library/doctest.rst:653

msgid ""

"When specified, display the first failing example in each doctest, but "

"suppress output for all remaining examples. This will prevent doctest from "

"reporting correct examples that break because of earlier failures; but it "

"might also hide incorrect examples that fail independently of the first "

"failure. When :const:`REPORT_ONLY_FIRST_FAILURE` is specified, the "

"remaining examples are still run, and still count towards the total number "

"of failures reported; only the output is suppressed."

msgstr ""

#: ../Doc/library/doctest.rst:664

msgid ""

"When specified, exit after the first failing example and don't attempt to "

"run the remaining examples. Thus, the number of failures reported will be at "

"most 1. This flag may be useful during debugging, since examples after the "

"first failure won't even produce debugging output."

msgstr ""

#: ../Doc/library/doctest.rst:669

msgid ""

"The doctest command line accepts the option ``-f`` as a shorthand for ``-o "

"FAIL_FAST``."

msgstr ""

#: ../Doc/library/doctest.rst:677

msgid "A bitmask or'ing together all the reporting flags above."

msgstr ""

#: ../Doc/library/doctest.rst:680

msgid ""

"There is also a way to register new option flag names, though this isn't "

"useful unless you intend to extend :mod:`doctest` internals via subclassing:"

msgstr ""

#: ../Doc/library/doctest.rst:686

msgid ""

"Create a new option flag with a given name, and return the new flag's "

"integer value. :func:`register_optionflag` can be used when subclassing :"

"class:`OutputChecker` or :class:`DocTestRunner` to create new options that "

"are supported by your subclasses. :func:`register_optionflag` should always "

"be called using the following idiom::"

msgstr ""

#: ../Doc/library/doctest.rst:702

msgid "Directives"

msgstr ""

#: ../Doc/library/doctest.rst:704

msgid ""

"Doctest directives may be used to modify the :ref:`option flags <doctest-"

"options>` for an individual example. Doctest directives are special Python "

"comments following an example's source code:"

msgstr ""

#: ../Doc/library/doctest.rst:715

msgid ""

"Whitespace is not allowed between the ``+`` or ``-`` and the directive "

"option name. The directive option name can be any of the option flag names "

"explained above."

msgstr ""

#: ../Doc/library/doctest.rst:719

msgid ""

"An example's doctest directives modify doctest's behavior for that single "

"example. Use ``+`` to enable the named behavior, or ``-`` to disable it."

msgstr ""

#: ../Doc/library/doctest.rst:722

msgid "For example, this test passes::"

msgstr ""

#: ../Doc/library/doctest.rst:728

msgid ""

"Without the directive it would fail, both because the actual output doesn't "

"have two blanks before the single-digit list elements, and because the "

"actual output is on a single line. This test also passes, and also requires "

"a directive to do so::"

msgstr ""

#: ../Doc/library/doctest.rst:736

msgid ""

"Multiple directives can be used on a single physical line, separated by "

"commas::"

msgstr ""

#: ../Doc/library/doctest.rst:742

msgid ""

"If multiple directive comments are used for a single example, then they are "

"combined::"

msgstr ""

#: ../Doc/library/doctest.rst:749

msgid ""

"As the previous example shows, you can add ``...`` lines to your example "

"containing only directives. This can be useful when an example is too long "

"for a directive to comfortably fit on the same line::"

msgstr ""

#: ../Doc/library/doctest.rst:757

msgid ""

"Note that since all options are disabled by default, and directives apply "

"only to the example they appear in, enabling options (via ``+`` in a "

"directive) is usually the only meaningful choice. However, option flags can "

"also be passed to functions that run doctests, establishing different "

"defaults. In such cases, disabling an option via ``-`` in a directive can "

"be useful."

msgstr ""

#: ../Doc/library/doctest.rst:767

msgid "Warnings"

msgstr ""

#: ../Doc/library/doctest.rst:769

msgid ""

":mod:`doctest` is serious about requiring exact matches in expected output. "

"If even a single character doesn't match, the test fails. This will "

"probably surprise you a few times, as you learn exactly what Python does and "

"doesn't guarantee about output. For example, when printing a set, Python "

"doesn't guarantee that the element is printed in any particular order, so a "

"test like ::"

msgstr ""

#: ../Doc/library/doctest.rst:778

msgid "is vulnerable! One workaround is to do ::"

msgstr ""

#: ../Doc/library/doctest.rst:783

msgid "instead. Another is to do ::"

msgstr ""

#: ../Doc/library/doctest.rst:791

msgid ""

"Before Python 3.6, when printing a dict, Python did not guarantee that the "

"key-value pairs was printed in any particular order."

msgstr ""

#: ../Doc/library/doctest.rst:794

msgid "There are others, but you get the idea."

msgstr ""

#: ../Doc/library/doctest.rst:796

msgid ""

"Another bad idea is to print things that embed an object address, like ::"

msgstr ""

#: ../Doc/library/doctest.rst:804

msgid ""

"The :const:`ELLIPSIS` directive gives a nice approach for the last example::"

msgstr ""

#: ../Doc/library/doctest.rst:809

msgid ""

"Floating-point numbers are also subject to small output variations across "

"platforms, because Python defers to the platform C library for float "

"formatting, and C libraries vary widely in quality here. ::"

msgstr ""

#: ../Doc/library/doctest.rst:820

msgid ""

"Numbers of the form ``I/2.**J`` are safe across all platforms, and I often "

"contrive doctest examples to produce numbers of that form::"

msgstr ""

#: ../Doc/library/doctest.rst:826

msgid ""

"Simple fractions are also easier for people to understand, and that makes "

"for better documentation."

msgstr ""

#: ../Doc/library/doctest.rst:833

msgid "Basic API"

msgstr ""

#: ../Doc/library/doctest.rst:835

msgid ""

"The functions :func:`testmod` and :func:`testfile` provide a simple "

"interface to doctest that should be sufficient for most basic uses. For a "

"less formal introduction to these two functions, see sections :ref:`doctest-"

"simple-testmod` and :ref:`doctest-simple-testfile`."

msgstr ""

#: ../Doc/library/doctest.rst:843

msgid ""

"All arguments except *filename* are optional, and should be specified in "

"keyword form."

msgstr ""

#: ../Doc/library/doctest.rst:846

msgid ""

"Test examples in the file named *filename*. Return ``(failure_count, "

"test_count)``."

msgstr ""

#: ../Doc/library/doctest.rst:849

msgid ""

"Optional argument *module_relative* specifies how the filename should be "

"interpreted:"

msgstr ""

#: ../Doc/library/doctest.rst:852

msgid ""

"If *module_relative* is ``True`` (the default), then *filename* specifies an "

"OS-independent module-relative path. By default, this path is relative to "

"the calling module's directory; but if the *package* argument is specified, "

"then it is relative to that package. To ensure OS-independence, *filename* "

"should use ``/`` characters to separate path segments, and may not be an "

"absolute path (i.e., it may not begin with ``/``)."

msgstr ""

#: ../Doc/library/doctest.rst:859

msgid ""

"If *module_relative* is ``False``, then *filename* specifies an OS-specific "

"path. The path may be absolute or relative; relative paths are resolved "

"with respect to the current working directory."

msgstr ""

#: ../Doc/library/doctest.rst:863

msgid ""

"Optional argument *name* gives the name of the test; by default, or if "

"``None``, ``os.path.basename(filename)`` is used."

msgstr ""

#: ../Doc/library/doctest.rst:866

msgid ""

"Optional argument *package* is a Python package or the name of a Python "

"package whose directory should be used as the base directory for a module-"

"relative filename. If no package is specified, then the calling module's "

"directory is used as the base directory for module-relative filenames. It "

"is an error to specify *package* if *module_relative* is ``False``."

msgstr ""

#: ../Doc/library/doctest.rst:872

msgid ""

"Optional argument *globs* gives a dict to be used as the globals when "

"executing examples. A new shallow copy of this dict is created for the "

"doctest, so its examples start with a clean slate. By default, or if "

"``None``, a new empty dict is used."

msgstr ""

#: ../Doc/library/doctest.rst:877

msgid ""

"Optional argument *extraglobs* gives a dict merged into the globals used to "

"execute examples. This works like :meth:`dict.update`: if *globs* and "

"*extraglobs* have a common key, the associated value in *extraglobs* appears "

"in the combined dict. By default, or if ``None``, no extra globals are "

"used. This is an advanced feature that allows parameterization of "

"doctests. For example, a doctest can be written for a base class, using a "

"generic name for the class, then reused to test any number of subclasses by "

"passing an *extraglobs* dict mapping the generic name to the subclass to be "

"tested."

msgstr ""

#: ../Doc/library/doctest.rst:886

msgid ""

"Optional argument *verbose* prints lots of stuff if true, and prints only "

"failures if false; by default, or if ``None``, it's true if and only if ``'-"

"v'`` is in ``sys.argv``."

msgstr ""

#: ../Doc/library/doctest.rst:890

msgid ""

"Optional argument *report* prints a summary at the end when true, else "

"prints nothing at the end. In verbose mode, the summary is detailed, else "

"the summary is very brief (in fact, empty if all tests passed)."

msgstr ""

#: ../Doc/library/doctest.rst:894

msgid ""

"Optional argument *optionflags* (default value 0) takes the :ref:`bitwise OR "

"<bitwise>` of option flags. See section :ref:`doctest-options`."

msgstr ""

#: ../Doc/library/doctest.rst:898

msgid ""

"Optional argument *raise_on_error* defaults to false. If true, an exception "

"is raised upon the first failure or unexpected exception in an example. "

"This allows failures to be post-mortem debugged. Default behavior is to "

"continue running examples."

msgstr ""

#: ../Doc/library/doctest.rst:903 ../Doc/library/doctest.rst:1043

msgid ""

"Optional argument *parser* specifies a :class:`DocTestParser` (or subclass) "

"that should be used to extract tests from the files. It defaults to a "

"normal parser (i.e., ``DocTestParser()``)."

msgstr ""

#: ../Doc/library/doctest.rst:907 ../Doc/library/doctest.rst:1047

msgid ""

"Optional argument *encoding* specifies an encoding that should be used to "

"convert the file to unicode."

msgstr ""

#: ../Doc/library/doctest.rst:913

msgid ""

"All arguments are optional, and all except for *m* should be specified in "

"keyword form."

msgstr ""

#: ../Doc/library/doctest.rst:916

msgid ""

"Test examples in docstrings in functions and classes reachable from module "

"*m* (or module :mod:`__main__` if *m* is not supplied or is ``None``), "

"starting with ``m.__doc__``."

msgstr ""

#: ../Doc/library/doctest.rst:920

msgid ""

"Also test examples reachable from dict ``m.__test__``, if it exists and is "

"not ``None``. ``m.__test__`` maps names (strings) to functions, classes and "

"strings; function and class docstrings are searched for examples; strings "

"are searched directly, as if they were docstrings."

msgstr ""

#: ../Doc/library/doctest.rst:925

msgid ""

"Only docstrings attached to objects belonging to module *m* are searched."

msgstr ""

#: ../Doc/library/doctest.rst:927

msgid "Return ``(failure_count, test_count)``."

msgstr ""

#: ../Doc/library/doctest.rst:929

msgid ""

"Optional argument *name* gives the name of the module; by default, or if "

"``None``, ``m.__name__`` is used."

msgstr ""

#: ../Doc/library/doctest.rst:932

msgid ""

"Optional argument *exclude_empty* defaults to false. If true, objects for "

"which no doctests are found are excluded from consideration. The default is "

"a backward compatibility hack, so that code still using :meth:`doctest."

"master.summarize` in conjunction with :func:`testmod` continues to get "

"output for objects with no tests. The *exclude_empty* argument to the newer :"

"class:`DocTestFinder` constructor defaults to true."

msgstr ""

#: ../Doc/library/doctest.rst:939

msgid ""

"Optional arguments *extraglobs*, *verbose*, *report*, *optionflags*, "

"*raise_on_error*, and *globs* are the same as for function :func:`testfile` "

"above, except that *globs* defaults to ``m.__dict__``."

msgstr ""

#: ../Doc/library/doctest.rst:946

msgid ""

"Test examples associated with object *f*; for example, *f* may be a string, "

"a module, a function, or a class object."

msgstr ""

#: ../Doc/library/doctest.rst:949

msgid ""

"A shallow copy of dictionary argument *globs* is used for the execution "

"context."

msgstr ""

#: ../Doc/library/doctest.rst:951

msgid ""

"Optional argument *name* is used in failure messages, and defaults to ``"

"\"NoName\"``."

msgstr ""

#: ../Doc/library/doctest.rst:954

msgid ""

"If optional argument *verbose* is true, output is generated even if there "

"are no failures. By default, output is generated only in case of an example "

"failure."

msgstr ""

#: ../Doc/library/doctest.rst:957

msgid ""

"Optional argument *compileflags* gives the set of flags that should be used "

"by the Python compiler when running the examples. By default, or if "

"``None``, flags are deduced corresponding to the set of future features "