| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
skipped on Mac OS X. Not sure yet about test_locale.py: this may be
due to my copy of Mac OS X (although it talks english fine enough).
|
|
|
|
| |
This should probably go into NEWS (who's responsible for that?).
|
| |
|
|
|
|
| |
changes from start of branch upto r22b2 were already merged, of course).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
the curses module. It's not run automatically; '-u curses' must be
specified as an argument to regrtest
|
| |
|
| |
|
| |
|
|
|
|
|
| |
error-reporting for the classic compare-expected-output tests.
Curiously, the bug consisted of not simplifying the logic enough!
|
|
|
|
|
|
|
| |
the local save/modify/restore of sys.stdout, but add machinery so that
regrtest can tell test_support the value of sys.stdout at the time
regrtest.main() started, and test_support can pass that out later to anyone
who needs a "visible" stdout.
|
|
|
|
| |
favor of local save/modify/restore. The test suite should run fine again.
|
|
|
|
|
|
|
| |
somewhere inside a line, use ndiff so that intraline difference marking
can point out what changed within a line. I don't remember diff-style
abbreviations either (haven't used it since '94, except to produce
patches), so say the rest in English too.
|
|
|
|
| |
XXX This should really be a unified diff, but I can't be bothered.
|
|
|
|
|
| |
output *and* doctest stuff. Assuming the doctest stuff comes after the
expected output, this fixes that.
|
|
|
|
|
|
|
|
|
|
| |
the first difference, let the test run till completion, then gather
all the output and compare it to the expected output using difflib.
XXX Still to do: produce diff output that only shows the sections that
differ; currently it produces ndiff-style output because that's the
easiest to produce with difflib, but this becomes a liability when the
output is voluminous and there are only a few differences.
|
|
|
|
| |
skipped test -- the print command already supplies a space.
|
|
|
|
| |
Add it back to the list of tests we expect to skip on Windows.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
horridly inefficient hack in regrtest's Compare class, but it's about as
clean as can be: regrtest has to set up the Compare instance before
importing a test module, and by the time the module *is* imported it's too
late to change that decision. The good news is that the more tests we
convert to unittest and doctest, the less the inefficiency here matters.
Even now there are few tests with large expected-output files (the new
cost here is a Python-level call per .write() when there's an expected-
output file).
|
|
|
|
|
|
|
|
| |
(1) Allow multiple -u options to extend each other (and the initial
value of use_resources passed into regrtest.main()).
(2) When a test is run stand-alone (not via regrtest.py), needed
resources are always granted.
|
|
|
|
| |
UnixWare 7.x systems.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag, which specifies external or resource intensive tests to
perform. This is used by test_largefile and test_socket_ssl.
-u/--use takes a comma separated list of flags, currently supported:
largefile, network.
usage(): New function. Note that the semantics of main() have changed
slightly; instead of returning an error code, it raises a
SystemExit (via sys.exit()) with the given error code.
main(): use_large_resources => use_resources
Also, added support for long-option alternative to the short
options.
_expectations: Added test_socket_ssl to the list of expectedly skipped
tests.
|
|
|
|
|
| |
Add test case to cover multiple future statements on separate lines of
a module.
|
|
|
|
|
| |
Otherwise printlist(surprise) will fail with a TypeError, because map
is called with an argument that doesn't support iteration.
|
|
|
|
| |
into indented lines each of which probably fits on a typical screen line).
|
|
|
|
|
| |
little bit using a dictionary to avoid more code duplication as
more platforms are supported.
|
| |
|
|
|
|
| |
about your platform too.
|
|
|
|
|
|
| |
name of the test, only write the output file if it already exists (and
tell the user to consider removing it). This avoids the generation of
unnecessary turds.
|
|
|
|
|
|
|
|
| |
When regrtest.py finds an attribute "test_main" in a test it imports,
regrtest runs the test's test_main after the import. test_threaded_import
needs this else the cross-thread import lock prevents it from making
progress. Other tests can use this hack too, but I doubt it will ever be
popular.
|
|
|
|
|
| |
contains a single line of text giving the name of the output file. This
covers all tests that do not actually produce any output in the test code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The changes cause compilation failures in any file in the Python
installation lib directory to cause the install to fail. It looks
like compileall.py intended to behave this way, but a change to
py_compile.py and a separate bug defeated it.
Fixes SF bug #412436
This change affects the test suite, which contains several files that
contain intentional errors. The solution is to extend compileall.py
with the ability to skip compilation of selected files.
In the test suite, rename nocaret.py and test_future[3..7].py to start
with badsyntax_nocaret.py and badsyntax_future[3..7].py. Update the
makefile to skip compilation of these files. Update the tests to use
the name names for imports.
NB compileall.py is changed so that compile_dir() returns success only
if all recursive calls to compile_dir() also check success.
|
|
|
|
|
| |
seven are not tests in their own right; these files are mentioned in
regrtest.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. When running in verbose mode, if any test happens to pass, print
a warning that the apparent success may be bogus (stdout isn't
compared in verbose mode). Been fooled by that too often.
2. When a test fails because the expected stdout doesn't match the
actual stdout, print as much of stdout as did match before the
first failing write. Else we get failures of the form "expected
'a', got 'b'" and a glance at the expected output file shows
500 instances of 'a' -- no idea where it failed, and, as in #1,
trying to run in verbose mode instead doesn't help because
stdout isn't compared then.
|
|
|
|
|
| |
Use != instead of <> since <> is documented as "obsolescent".
Use "is" and "is not" when comparing with None or type objects.
|
| |
|
|
|
|
|
|
| |
First, only report garbage that the GC cannot free. Second, only report
the number of objects found, not their repr(). People can dig deeper on
their own if they find a leak.
|
|
|
|
| |
used to find cyclic garbage produced by tests.
|
|
|
|
| |
name and the ":" that separates it from the value. (Minor cleanup.)
|
|
|
|
| |
re-raise it instead of re-raising it "manually" the ugly way.
|