| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
change to regrtest.py to allow optional running of test_largefile ('cause it's
slow on Win64).
This closes patches:
http://sourceforge.net/patch/index.php?func=detailpatch&patch_id=100510&group_id=5470
and
http://sourceforge.net/patch/index.php?func=detailpatch&patch_id=100511&group_id=5470
|
| |
|
|
| |
mark the test as 'skipped', rather than 'failed'.
|
| |
|
|
| |
module is importable.
|
| |
|
|
|
|
|
|
|
|
| |
comments, docstrings or error messages. I fixed two minor things in
test_winreg.py ("didn't" -> "Didn't" and "Didnt" -> "Didn't").
There is a minor style issue involved: Guido seems to have preferred English
grammar (behaviour, honour) in a couple places. This patch changes that to
American, which is the more prominent style in the source. I prefer English
myself, so if English is preferred, I'd be happy to supply a patch myself ;)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Compare close contains a close method that checks to see if there
is any unconsumed data in the Compare instance; i.e. if the canonical
output file contains more data than was produced by the current test
run. This method was never called, allowing differences to go
undetected.
Fix is to call close after the test is run (after __import__)
output/test_long and output/test_popen2 needed trivial changes
output/test_select contained lots of text, but test_select.py produced
no output
|
| |
|
|
|
|
|
|
|
| |
allows the caller to execute the various tests in pseudo-random order -
default is still to execute tests in the order returned by findtests().
* moved initialization of the various flag variables to the main() function
definition, making it possible to execute regrtest.main() interactively
and still override default behavior.
|
| |
|
|
|
|
|
|
| |
weird errors. (E.g. see thread "weird bug in test_winreg" in python-dev.)
Since it's actually useful to be able to re-run an individual test
after running test.autotest, we keep the unloading code, but only for
modules whose full name starts with "test.".
|
| |
|
|
|
| |
after each test has been run. This avoids excessive memory growth
during the tests.
|
| |
|
|
|
| |
With -s only a single test is run. The next test run is chosen
sequentially from the list of all tests.
|
| |
|
|
|
|
| |
by the new '-x' arguments, losing the previous items. Thus,
test_support, test_b1 & test_b2 are executed (and warnings issued).
(Discovered by Vladimir Marangozov.)
|
| | |
|
| |
|
|
| |
Kuchling @ CNRI.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
reporting a "crash".
Use sys.exc_info() instead of sys.exc_type and sys.exc_value.
|
| |
|
|
|
|
|
| |
it will run as package test, e.g. this will run the test suite:
import test.regrtest
test.regrtest.main()
|
| |
|
|
|
|
| |
default and -v. In default mode, the name of each test is printed.
-v is the same as the old -vv. -q is more quiet than the old default
mode; that's fine I think.
|
| |
|
|
|
| |
status from main() and call sys.exit(main()) in the startup stub at
the end of the file.
|
| | |
|
| | |
|
| |
|
|
|
| |
this mode, all tests are run in verbose mode with their output to
stdout. No comparing of output is done.
|
| |
|
