| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
branch into the trunk. This adds a new sys._current_frames()
function, which returns a dict mapping thread id to topmost
thread stack frame.
|
| |
|
|
| |
test_support.reap_children().
|
| | |
|
| |
|
|
| |
started after line 256.
|
| |
|
|
| |
rather than longs. This also fixes the test for eval(-sys.maxint - 1).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The hppa ubuntu box sometimes hangs forever in these tests. My guess
is that the wait is failing for some reason. Use WNOHANG, so we won't
wait until the buildbot kills the test suite.
I haven't been able to reproduce the failure, so I'm not sure if
this will help or not. Hopefully, this change will cause the test
to fail, rather than hang. That will be better since we will get
the rest of the test results. It may also help us debug the real problem.
*** The reason this originally failed was because there were many
zombie children outstanding before rev 47158 cleaned them up.
There are still hangs in test_subprocess that need to be addressed,
but that will take more work. This should close some holes.
|
| |
|
|
| |
specific encodings.
|
| | |
|
| |
|
|
| |
Python 2.6
|
| |
|
|
| |
returns a borrowed ref. Many of the calls are open to attack.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
str() or repr()) would work, just not multi-value tuples. Probably not a
backport candidate, since it changes the behaviour of passing a
single-element tuple:
>>> string.Template("$foo").substitute(dict(foo=(1,)))
'(1,)'
versus
'1'
|
| | |
|
| |
|
|
| |
and atof().
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
handler would cause a segfault. This merges in Expat's lib/xmlparse.c
revisions 1.154 and 1.155, which fix this and a closely related problem
(the later does not affect Python).
Moved the crasher test to the tests for xml.parsers.expat.
|
| | |
|
| |
|
|
| |
itself correctly.
|
| | |
|
| |
|
|
|
|
| |
It makes the error message consistent and always sends to stderr.
It would be much better for all the networking tests to hit only python.org.
|
| |
|
|
|
|
|
|
|
|
| |
be called at the end of each test that spawns children (perhaps it
should be called from regrtest instead?). This will hopefully prevent
some of the unexplained failures in the buildbots (hppa and alpha)
during tests that spawn children. The problems were not reproducible.
There were many zombies that remained at the end of several tests.
In the worst case, this shouldn't cause any more problems,
though it may not help either. Time will tell.
|
| |
|
|
|
|
|
| |
(modified patch by Sam Ruby; changed to use separate REs for start and end
tags to reduce matching cost for end tags; extended tests; updated to avoid
breaking previous changes to support IPv6 addresses in unquoted attribute
values)
|
| | |
|
| |
|
|
| |
to something else (like '__main__')
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
consistent with os.wait() returning immediately because some other
subprocess had previously exited; the test suite then immediately
tries to lock the mailbox and gets an error saying it's already
locked.
To fix this, do a waitpid() so the test suite only continues once
the intended child process has exited.
|
| | |
|
| |
|
|
|
| |
On slow machines, maybe the time intervals (2 sec, 0.5 sec) will be too tight.
I'll see how the buildbots like it.
|
| |
|
|
|
|
|
|
|
|
| |
('[' and ']' were not accepted in unquoted attribute values)
- cleaned up tests of character and entity reference decoding so the
tests cover the documented relationships among handle_charref,
handle_entityref, convert_charref, convert_codepoint, and
convert_entityref, without bringing up Unicode issues that sgmllib
cannot be involved in
|
| |
|
|
| |
test_support.is_resource_enabled.
|
| |
|
|
|
|
|
| |
both a subclass of Warning and a subclass of types.ClassType. The latter is no
longer true thanks to new-style exceptions.
Closes bug #1510580. Thanks to AMK for the test.
|
| |
|
|
| |
Test for correct lineno on list, tuple, dict literals.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem of checking too eagerly for recursive calls is the
following: if a RuntimeError is caused by recursion, and if code needs
to normalize it immediately (as in the 2nd test), then
PyErr_NormalizeException() needs a call to the RuntimeError class to
instantiate it, and this hits the recursion limit again... causing
PyErr_NormalizeException() to never finish.
Moved this particular recursion check to slot_tp_call(), which is not
involved in instantiating built-in exceptions.
Backport candidate.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
constructor, meaning it is treated as *args, not as a single argument. This
means using the 'message' attribute won't work (until Py3K comes around),
and so one must grab from 'arg' to get the error number.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
os.environ (setting envar COLUMNS), which at least caused
test_float_default() to fail if the tests were run more than once.
This repairs the test_optparse -R failures Neal reported on
python-dev. It also explains some seemingly bizarre test_optparse
failures we saw a couple weeks ago on the buildbots, when
test_optparse failed due to test_file failing to clean up after
itself, and then test_optparse failed in an entirely different
way when regrtest's -w option ran test_optparse a second time.
It's now obvious that make_parser() permanently changing os.environ
was responsible for the second half of that.
|
| |
|
|
| |
as reported by Neal on python-dev.
|
| |
|
|
|
| |
is_term_resized, resize_term and resizeterm. This uses three
separate configure checks (one for each function).
|
| | |
|
| |
|
|
| |
typeobject.c.
|
| | |
|
