summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* - Added __docformat__Edward Loper2004-08-122-17/+33
| | | | | | | - Added comments for some regexps - If the traceback type/message don't match, then still print full traceback in report_failure (not just the first & last lines) - Renamed DocTestRunner.__failure_header -> _failure_header
* - Changed option directives to be example-specific. (i.e., they nowEdward Loper2004-08-122-79/+254
| | | | | | | | | modify option flags for a single example; they do not turn options on or off.) - Added "indent" and "options" attributes for Example - Got rid of add_newlines param to DocTestParser._parse_example (it's no longer needed; Example's constructor now takes care of it). - Added some docstrings
* - Added a register_optionflag function (so users can add their ownEdward Loper2004-08-121-22/+18
| | | | | option flags); and use it to define the existing optionflag constants.
* avoid version numbers in the text where possibleFred Drake2004-08-101-5/+5
|
* clarify the behavior of the .first() and .last() methods for emptyFred Drake2004-08-101-0/+2
| | | | | | databases this should be backported to the release23-maint branch
* Spelling fixAndrew M. Kuchling2004-08-101-1/+1
|
* added missing documentation for UseForeignDTD() (new in 2.3)Fred Drake2004-08-101-0/+21
| | | | someone should backport to the release23-maint branch
* add descriptions for many of the new error codesFred Drake2004-08-101-1/+82
|
* minor changes to make this format againFred Drake2004-08-101-2/+2
|
* Start rewriting doctest's LaTeX docs. Damn, this is slow going!Tim Peters2004-08-102-29/+148
|
* Fix typo in getquotaroot parameter reported by Thierry FLORAC. Also amplify ↵Piers Lauder2004-08-101-3/+5
| | | | doc string for select to indicate proper way to obtain other responses.
* Whitespace normalization.Tim Peters2004-08-095-5/+1
|
* [Patch #1005465] Markup tweaksAndrew M. Kuchling2004-08-091-1/+2
|
* [Patch #1005491 ] use __name__ == '__main__' in scriptsAndrew M. Kuchling2004-08-0934-211/+268
|
* Edward's latest checkins somehow managed to wipe out my previous latestTim Peters2004-08-092-15/+17
| | | | checkins. Reapplying the latter changes.
* - DocTest is now a simple container class; its constructor is no longerEdward Loper2004-08-092-105/+111
| | | | | | | | | | | responsible for parsing the string. - Renamed Parser to DocTestParser - DocTestParser.get_*() now accept the string & name as command-line arguments; the parser's constructor is now empty. - Added DocTestParser.get_doctest() method - Replaced "doctest_factory" argument to DocTestFinder with a "parser" argument (takes a DocTestParser). - Changed _tag_msg to take an indentation string argument.
* This started as a spelling and whitespace cleanup. The comment forTim Peters2004-08-092-20/+22
| | | | | | | | | the set_trace fiddling didn't make sense to me, and I ended up reworking that part of the code. We really do want to save and restore pdb.set_trace, so that each dynamically nested level of doctest gets sys.stdout fiddled to what's appropriate for *it*. The only "trick" really needed is that these layers of set_trace wrappers each call the original pdb.set_trace (instead of the current pdb.set_trace).
* Patch #1006003: Cygwin standard module build problemsJason Tishler2004-08-092-3/+4
| | | | Add missing PyAPI_FUNC/PyAPI_DATA macros.
* Add itemAndrew M. Kuchling2004-08-091-0/+4
|
* - make a module reference a hyperlinkFred Drake2004-08-091-2/+3
| | | | - wrap a long line
* fix markup nitFred Drake2004-08-091-1/+2
|
* Bug #1001857: socketmodule does not build under cygwinJason Tishler2004-08-091-0/+4
| | | | Restore clean building under Cygwin.
* Added support for pdb.set_trace.Jim Fulton2004-08-092-1/+103
|
* Ooops - for some reason I had the wrong versionadded...Dave Cole2004-08-091-1/+1
|
* Patch #1003700: Add socketpair function to socket module.Dave Cole2004-08-097-0/+130
|
* Removed lots of stuff from the module docstring. My intent for 2.4 isTim Peters2004-08-091-137/+18
| | | | | to put details in the LaTeX docs instead, and lots of stuff in the module docstring wasn't useful anyway.
* Repair some out-of-date comments.Tim Peters2004-08-091-8/+2
|
* Drop the excruciating newline requirements on arguments toTim Peters2004-08-092-32/+42
| | | | | | Example.__init__. The constructor now adds trailing newlines when needed, and no longer distinguishes between multi- and single-line cases for source.
* Give return stmts their own lines.Tim Peters2004-08-091-2/+4
|
* Indent body of _EXAMPLE_RE for readability. _IS_BLANK_OR_COMMENT makesTim Peters2004-08-091-13/+13
| | | | more sense as a callable.
* Changed Parser.get_examples() to return a list of Example objects,Edward Loper2004-08-091-21/+13
| | | | rather than a list of triples.
* - Split DocTestRunner's check_output and output_difference methods offEdward Loper2004-08-091-127/+139
| | | | | | into their own class, OutputChecker. - Added optional OutputChecker arguments to DocTestRunner, DocTestCase, DocTestSuite.
* Rewrote Parser, using regular expressions instead of walking thoughEdward Loper2004-08-092-221/+227
| | | | | | | | | the string one line at a time. The resulting code is (in my opinion, anyway), much easier to read. In the process, I found and fixed a bug in the orginal parser's line numbering in error messages (it was inconsistant between 0-based and 1-based). Also, check for missing blank lines after the prompt on all prompt lines, not just PS1 lines (test added).
* Fixed doctest error (wrong prompts)Edward Loper2004-08-091-3/+3
|
* Previous commit was viewed as "perverse". Changed to just cast the unusedBrett Cannon2004-08-081-1/+3
| | | | | | variable to void.. Thanks to Sjoerd Mullender for the suggested change.
* Add a test for Context.copy().Raymond Hettinger2004-08-081-0/+8
|
* Tell unittest that source files with "badsyntax" in their names shouldTim Peters2004-08-081-1/+5
| | | | | raise SyntaxError. test_compiler passes now on WinXP, at least in a release-build non-O run.
* Renamed locals to better reflect their meanings.Tim Peters2004-08-081-6/+6
|
* In verbose mode, display the name of each file before trying to compileTim Peters2004-08-081-1/+4
| | | | | it. Else when this fails, there's no way to tell which file it was chewing on.
* Brief xrange news.Tim Peters2004-08-081-1/+3
|
* Bug 1003935: xrange overflowsTim Peters2004-08-083-11/+37
| | | | | | | | | | | | | | | Added XXX comment about why the undocumented PyRange_New() API function is too broken to be worth the considerable pain of repairing. Changed range_new() to stop using PyRange_New(). This fixes a variety of bogus errors. Nothing in the core uses PyRange_New() now. Documented that xrange() is intended to be simple and fast, and that CPython restricts its arguments, and length of its result sequence, to native C longs. Added some tests that failed before the patch, and repaired a test that relied on a bogus OverflowError getting raised.
* Trimmed trailing whitespace.Tim Peters2004-08-081-5/+5
|
* Get rid of the ignore_imports argument to DocTestFinder.find().Tim Peters2004-08-083-41/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This got slammed in when find() was fixed to stop grabbing doctests from modules imported *by* the module being tested. Such tests cannot be expected to succeed, since they'll be run with the current module's globals. Dozens of Zope3 doctests were failing because of that. It wasn't clear why ignore_imports got added then. Maybe it's because some existing tests failed when the change was made. Whatever, it's a Bad Idea so it's gone now. The only use of it was exceedingly obscure, in test_doctest's "Duplicate Removal" test. It was "needed" there because, as an artifact of running a doctest inside a doctest, the func_globals of functions compiled in the second-level doctest don't match the module globals, and so the test-finder believed these functions were from a foreign module and skipped them. But that took a long time to figure out, and I actually understand some of this stuff <0.9 wink>. That problem was resolved by moving the source code for the second-level doctest into an actual module (test/doctest_aliases.py). The only remaining difficulty was that the test for the deprecated Tester.rundict() then failed, because the test finder doesn't take module=None at face value, trying to guess which module the user really intended then. Its guess wasn't appropriate for what Tester.rundict needs when module=None is given to *it*, which is "no, there is no module here, and I mean it". So now passing module=False means exactly that. This is hokey, but ignore_imports=False was really a hack to worm around that there was no way to tell the test-finder that module=None *sometimes* means what it says. There was no use case for the combination of passing a real module with ignore_imports=False.
* * Context.copy() now makes a deepcopy.Raymond Hettinger2004-08-081-12/+21
| | | | * Facilitate reloads of local thread.
* Type in docstring.Tim Peters2004-08-081-1/+1
|
* Also deprecated the old Tester class, which is no longer used by anythingTim Peters2004-08-082-7/+33
| | | | except internal tests.
* Deprecate the doctest.is_private() function.Tim Peters2004-08-081-0/+6
|
* Deprecated testmod's useless & confusing isprivate gimmick.Tim Peters2004-08-082-61/+32
| | | | | | | Ripped out the docs for the new DocTestFinder's namefilter argument, and renamed it to _namefilter; this only existed to support isprivate. Removed the new DocTestFinder's objfilter argument. No point adding more cruft to a broken filtering design.
* Whitespace normalization.Tim Peters2004-08-082-6/+3
|
* Bug 1003471: Python 1.5.2 security vulnerability still present in 2.3.4Tim Peters2004-08-081-4/+10
| | | | | | | | | | | | | | That's the title of the report, but the hole was probably plugged since Python 2.0. See corresponding checkin to PC/getpathp.c: a crucial precondition for joinpath() was neither documented nor verified, and there are so many callers with so many conditional paths that no "eyeball analysis" is satisfactory. Now Python dies with a fatal error if the precondition isn't satisfied, instead of allowing a buffer overrun. NOT TESTED! The Windows version of the patch was, but not this one. I don't feel like waiting for someone to notice the patch I attached to the bug report. If it doesn't compile, sorry, but fix it <wink>. If it does compile, it's "obviously correct".