summaryrefslogtreecommitdiffstats
path: root/Lib/doctest.py
Commit message (Collapse)AuthorAgeFilesLines
* Stronger tests for combinatoric relationships.Raymond Hettinger2009-01-271-0/+4
|
* Issue #4197: Fix the remaining part of the doctest-in-zipfile problem by ↵Nick Coghlan2008-12-151-3/+13
| | | | giving linecache access to the module globals when available
* patch from issue 1108Skip Montanaro2008-11-191-2/+2
|
* #2767: don't clear globs in run() call, since they could be needed in tearDown,Georg Brandl2008-05-121-1/+1
| | | | which clears them at the end.
* #2766: remove code without effect.Georg Brandl2008-05-121-2/+0
|
* Doctest results return a named tuple for readabilityRaymond Hettinger2008-01-111-12/+15
|
* Fix issue #1530.Alexandre Vassalotti2007-12-081-3/+6
| | | | Return an error exit status if not all tests passes.
* Replaced import of the 'new' module with 'types' module and added a ↵Christian Heimes2007-11-271-4/+4
| | | | deprecation warning to the 'new' module.
* back in these go - thanks to Titus Brown for the fixSkip Montanaro2007-11-241-0/+13
|
* revert change that breaks test_doctest (which I forgot to run - sorry)Skip Montanaro2007-11-241-11/+0
|
* Make trace and doctest play nice together (issue 1429818). Will backport.Skip Montanaro2007-11-231-0/+11
|
* doctest assumed that a package's __loader__.get_data() method used universalBrett Cannon2007-11-211-1/+4
| | | | | | | newlines; it doesn't. To rectify this the string returned replaces all instances of os.linesep with '\n' to fake universal newline support. Backport candidate.
* Small nit, found by Neal.Georg Brandl2007-03-061-2/+2
|
* Patch #1663234: you can now run doctest on test files and modulesGeorg Brandl2007-03-061-2/+17
| | | | using "python -m doctest [-v] filename ...".
* Fix a couple of typos.Neal Norwitz2006-08-291-2/+2
|
* Bug #1529297: The rewrite of doctest for Python 2.4 unintentionallyTim Peters2006-07-271-0/+5
| | | | | lost that tests are sorted by name before being run. ``DocTestFinder`` has been changed to sort the list of tests it returns.
* Remove unused importNeal Norwitz2006-06-121-1/+1
|
* Remove doctest.testmod's deprecated (in 2.4) `isprivate`Tim Peters2006-06-051-76/+9
| | | | argument. A lot of hair went into supporting that!
* Whitespace normalization.Tim Peters2006-05-301-3/+3
|
* ("Forward-port" of r46506)Armin Rigo2006-05-281-5/+6
| | | | | | | | | | | | | | Remove various dependencies on dictionary order in the standard library tests, and one (clearly an oversight, potentially critical) in the standard library itself - base64.py. Remaining open issues: * test_extcall is an output test, messy to make robust * tarfile.py has a potential bug here, but I'm not familiar enough with this code. Filed in as SF bug #1496501. * urllib2.HTTPPasswordMgr() returns a random result if there is more than one matching root path. I'm asking python-dev for clarification...
* Patch #1080727: add "encoding" parameter to doctest.DocFileSuiteGeorge Yoshida2006-05-281-2/+17
| | | | Contributed by Bjorn Tillenius.
* Patch #721464: pdb.Pdb instances can now be given explicit stdin andGeorg Brandl2006-05-101-1/+1
| | | | | stdout arguments, making it possible to redirect input and output for remote debugging.
* Variant of patch #1478292. doctest.register_optionflag(name)Tim Peters2006-05-101-3/+2
| | | | | shouldn't create a new flag when `name` is already the name of an option flag.
* Patch #1475231: add a new SKIP doctest option, thanks toTim Peters2006-04-251-0/+9
| | | | Edward Loper.
* Updated the warnings, linecache, inspect, traceback, site, and doctest modulesPhillip J. Eby2006-04-111-11/+15
| | | | | to work correctly with modules imported from zipfiles or via other PEP 302 __loader__ objects. Tests and doc updates are included.
* Fix test cases for doctest.Georg Brandl2005-06-261-0/+1
|
* bug [ 1172785 ] doctest.script_from_examples() result sometimes un-exec-ableGeorg Brandl2005-06-261-1/+2
|
* SF patch 1167316: doctest.py fails self-test if run directly.Tim Peters2005-03-281-5/+5
| | | | | | Patch by Ilya Sandler. Bugfix candidate.
* add __file__ to the globals available for tests loaded via DocFileSuite;Fred Drake2004-12-211-0/+4
| | | | | this is useful for locating supporting data files, just as it is in Python modules
* And delete a useless comment.Tim Peters2004-11-081-1/+0
|
* _OutputRedirectingPdb.trace_dispatch(): Return the base class'sTim Peters2004-11-081-4/+5
| | | | trace_dispatch() result in a more obvious, and more robust way.
* test_doctest.py test_pdb_set_trace_nested(): A new test from Jim FultonTim Peters2004-11-081-3/+2
| | | | | | | | | showing that doctest's pdb.set_trace() support was dramatically broken. doctest.py _OutputRedirectingPdb.trace_dispatch(): Return a local trace function instead of (implicitly) None. Else interaction with pdb was bizarre, noticing only 'call' events. Amazingly, the existing set_trace() tests didn't care.
* Fixed a small bug. doctest didn't handle unicode docstrings containingJim Fulton2004-10-131-1/+3
| | | | non-ascii characters.
* Reverted the addition of a NORMALIZE_NUMBERS option, per Tim Peter'sEdward Loper2004-09-281-79/+1
| | | | | | | | request. Tim says that "correct 'fuzzy' comparison of floats cannot be automated." (The motivation behind adding the new option was verifying interactive examples in Python's latex documentation; several such examples use numbers that don't print consistently on different platforms.)
* Added a new NORMALIZE_NUMBERS option, which causes number literals inEdward Loper2004-09-281-1/+79
| | | | | the expected output to match corresponding number literals in the actual output if their values are equal (to ten digits of precision).
* - Added a "parser" option to testfile() and DocFileTest().Edward Loper2004-09-271-5/+12
|
* Removed debug_script from the public API: no docs, not public. I'm inTim Peters2004-09-261-1/+0
| | | | | the process of writing docs for the other "missing" debug support functions.
* Add set_unittest_reportflags() to the public API. Docs will followTim Peters2004-09-261-0/+1
| | | | "soon", after I repair the LaTeX I somehow damaged.
* Removed two undocumented unittest support classes, and one undocumentedTim Peters2004-09-261-3/+0
| | | | | unittest support function, from the public interface. If they're not documented, they shouldn't be public.
* Removed most of the module docstring. There's too much to explain now,Tim Peters2004-09-251-124/+2
| | | | and the LaTeX docs are in increasingly good shape.
* - Minor docstring fixes.Edward Loper2004-09-211-15/+9
| | | | - Simplified code to find names for file-based tests.
* Whitespace normalization.Tim Peters2004-09-201-4/+4
|
* - Added "testfile" function, a simple function for running & verifyingEdward Loper2004-09-191-37/+183
| | | | | | | | all examples in a given text file. (analagous to "testmod") - Minor docstring fixes. - Added module_relative parameter to DocTestFile/DocTestSuite, which controls whether paths are module-relative & os-independent, or os-specific.
* In DocFileTest:Edward Loper2004-09-181-3/+20
| | | | | | | - Fixed bug in handling of absolute paths. - If run from an interactive session, make paths relative to the directory containing sys.argv[0] (since __main__ doesn't have a __file__ attribute).
* exclude_empty: make the default True for DocTestFinder, and introduce itTim Peters2004-09-131-7/+7
| | | | | | | with default False for testmod(). The real point of introducing this was so that output from doctest.master.summarize() would be the same as in 2.3, and doctest.master in 2.4 is a backward-compatability hack used only by testmod().
* Added new parameter exclude_empty to DocTestFinder.__init__, whichEdward Loper2004-09-131-8/+14
| | | | | controls whether tests are included for objects with empty docstrings. Defaults to True, to match the behavior of Python 2.3.
* DocTestFinder._find(): for tests derived from a module __test__ global,Tim Peters2004-09-131-1/+1
| | | | | doctest always promised to stick "__test__" in the name. That got broken. Now it's fixed again.
* Reluctantly, rehabilitate doctest.master.Tim Peters2004-09-131-9/+26
|
* Tester.run___test__(): This couldn't possibly work at all. I'm afraidTim Peters2004-09-121-1/+1
| | | | the "backward compatibility" here was a joke.
* Tester.__init__(): this couldn't possibly work when a module argumentTim Peters2004-09-121-1/+1
| | | | was passed.