| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
[ 1005248 ] new.code() not cleanly checking its arguments
using the result of new.code() can still destroy the sun, but merely
calling the function shouldn't any more.
I also rewrote the existing tests of new.code() to use vastly less
un-bogus arguments, and added tests for the previous insane behaviours.
|
| |
|
| |
|
| |
|
|
|
|
| |
Backported to 2.3.
|
|
|
|
| |
Backported to 2.3.
|
|
|
|
|
| |
(rather than replacing <BLANKLINE> with blank lines in `got`). This
makes it easier to see what's intended.
|
|
|
|
|
|
|
|
| |
visually distinguish the expected output from the comments (use
"##" to mark expected outputs, and "#" to mark comments).
- If the string given to DocTestParser.get_program() is indented, then
strip its indentation. (In particular, find the min indentation of
non-blank lines, and strip that indentation from all lines.)
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
option flags); and use it to define the existing optionflag
constants.
|
| |
|
|
|
|
|
|
| |
databases
this should be backported to the release23-maint branch
|
| |
|
|
|
|
| |
someone should backport to the release23-maint branch
|
| |
|
| |
|
| |
|
|
|
|
| |
doc string for select to indicate proper way to obtain other responses.
|
| |
|
| |
|
| |
|
|
|
|
| |
checkins. Reapplying the latter changes.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
Add missing PyAPI_FUNC/PyAPI_DATA macros.
|
| |
|
|
|
|
| |
- wrap a long line
|
| |
|
|
|
|
| |
Restore clean building under Cygwin.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
to put details in the LaTeX docs instead, and lots of stuff in the
module docstring wasn't useful anyway.
|
| |
|
|
|
|
|
|
| |
Example.__init__. The constructor now adds trailing newlines when
needed, and no longer distinguishes between multi- and single-line
cases for source.
|
| |
|
|
|
|
| |
more sense as a callable.
|
|
|
|
| |
rather than a list of triples.
|
|
|
|
|
|
| |
into their own class, OutputChecker.
- Added optional OutputChecker arguments to DocTestRunner,
DocTestCase, DocTestSuite.
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
| |
variable to void..
Thanks to Sjoerd Mullender for the suggested change.
|
| |
|
|
|
|
|
| |
raise SyntaxError. test_compiler passes now on WinXP, at least in a
release-build non-O run.
|
| |
|
|
|
|
|
| |
it. Else when this fails, there's no way to tell which file it was
chewing on.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|