| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
| |
os.startfile is not present.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
least as big as a long. I believe this to be a safe assumption that is being
made in many parts of CPython, but a check could be added.
len(xrange(sys.maxint)) works now, so fix the testsuite's odd exception for
64-bit platforms too. It also fixes 'zip(xrange(sys.maxint), it)' as a
portable-ish (if expensive) alternative to enumerate(it); since zip() now
calls len(), this was breaking on (real) 64-bit platforms. No additional
test was added for that behaviour.
|
| | |
|
| |
|
|
|
| |
is 'python'. But 'python' is actually a directory, 'python.exe' is the
executable.
|
| |
|
|
|
|
|
|
| |
- The buildbot "fetch it" step failed at the end, due to
using Unix syntax in the final "copy the DLL" step.
test_sqlite was skipped as a result.
- test_sqlite is no longer an expected skip on Windows.
|
| |
|
|
| |
Re-enable all the tests in test_trace.py except one. Still not sure that these tests test what they used to test, but they pass. One failing test seems to be caused by undocumented line number table behavior in Python 2.4.
|
| | |
|
| | |
|
| |
|
|
| |
Jeremy, please fix this correctly after the alpha.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tracing/line number table in except blocks.
Reflow long lines introduced by col_offset changes. Update test_ast
to handle new fields in excepthandler.
As note in Python.asdl says, we might want to rethink how attributes
are handled. Perhaps they should be the same as other fields, with
the primary difference being how they are defined for all types within
a sum.
Also fix asdl_c so that constructors with int fields don't fail when
passed a zero value.
|
| | |
|
| | |
|
| |
|
|
| |
lookup to use the IP address returned by gethosbyname.
|
| |
|
|
|
|
|
|
|
| |
converted to CR CR NL. There may be a way to fix this with tcsetattr,
but I couldn't find it. There was a similar problem on IRIX.
Just normalize the output and compare that.
Will backport.
|
| |
|
|
|
|
|
|
|
| |
like cause the interpreter to exit abruptly. If there's a way to fix this,
it would be good to really fix it. It could just be the operation of the
std C library and we just aren't supposed to do that.
When the test case is skipped, we print a message so the user can check
for themselves.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
now sport attributes that provide access to the parts of the result.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The
s.connect(("gmail.org", 995))
line has been timing out on all buildbot slaves for hours
now, causing the test to fail.
|
| |
|
|
|
|
|
| |
This is based on pysqlite2.1.3, and provides a DB-API interface in
the standard library. You'll need sqlite 3.2.2 or later to build
this - if you have an earlier version, the C extension module will
not be built.
|
| |
|
|
| |
work, this time by ugly brute force.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
that have __private names in their __slots__.
|
| | |
|
| |
|
|
| |
failures gracefully
|
| |
|
|
| |
e.g. IndentationError. (bug #1447885)
|
| |
|
|
|
|
| |
we are about to leave behind. An example of the cause of this leak can be
found in the leakers directory, in case we ever want to tackle the
underlying problem.
|
| |
|
|
|
| |
module. It's possible to generate HTML calendar now and the module can be
called as a script (e.g. via ``python -mcalendar``).
|
| |
|
|
|
|
|
|
| |
effect at the time test_decimal was imported. Else
running test_decimal had the bad side effect of
permanently changing the decimal context in effect.
That caused text_tokenize to fail if it ran after
test_decimal.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The doctests in decistmt() weren't run at all when
test_tokenize was run via regrtest.py.
- Some expected output in decistmt() was Windows-specific
(but nobody noticed because the doctests weren't getting
run).
- test_roundtrip() didn't actually test anything when
running the tests with -O. Now it does.
- Changed test_roundtrip() to show the name of the input
file when it fails. That would have saved a lot of
time earlier today.
- Added a bunch of comments.
|
| |
|
|
|
|
| |
adds the following API calls: PySet_Clear(), _PySet_Next(), and
_PySet_Update(). The latter two are considered non-public. Tests and
documentation (for the public API) are included.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is from the SF tracker as well; for some reason the
content of test_index.py was lost and an empty file was
checked in instead.
|
| | |
|
| |
|
|
| |
Fix the hit and miss style of testing for sets and dicts.
|
| | |
|
| |
|
|
| |
with title().
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
itertools.tee->instance->attribute->itertools.tee and
itertools.tee->teedataobject->itertools.tee cycles, which can be found now
that itertools.tee and its teedataobject participate in GC, remain findable
and cleanable. The test won't fail when they aren't, but at least the
frequent hunt-refleaks runs would spot the rise in refleaks.
|