| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
iterable object. I'm not sure how that got overlooked before!
Got rid of the internal _PySequence_IterContains, introduced a new
internal _PySequence_IterSearch, and rewrote all the iteration-based
"count of", "index of", and "is the object in it or not?" routines to
just call the new function. I suppose it's slower this way, but the
code duplication was getting depressing.
|
| |
|
|
|
|
|
|
|
| |
saving instead a traceback string, but test_support's run_unittest was
still peeking into unittest internals and trying to pick apart unittest's
errors and failures vectors as if they contained exc_info() tuples instead
of strings.
Whatever, when a unittest-based test failed, test_support blew up. I'm
not sure this is the right way to fix it; it simply gets me unstuck.
|
| | |
|
| |
|
|
| |
Also remove mappings that are not registered with IANA, and not extensions.
|
| |
|
|
| |
branch (if it ever gets to the typo, the test is failing anyway).
|
| |
|
|
|
|
|
|
| |
capabilities of the Pentium FPU, so what should have been (and were on
Windows) exact results got fuzzy. Then it turns out test_support.fcmp()
isn't tolerant of tiny errors when *one* of the comparands is 0, but
test_complex's old check_close_real() is. Rather than fix gcc <wink>,
easier to revert this test and revisit after the release.
|
| |
|
|
| |
existed when I wrote this test.
|
| | |
|
| | |
|
| |
|
|
| |
(Steve, can you add this to the PyUnit repository as well?)
|
| |
|
|
|
|
|
|
| |
(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.
|
| |
|
|
| |
This covers regression on SF bug #458860.
|
| |
|
|
| |
This closes SF bug #458860.
|
| |
|
|
| |
support.
|
| |
|
|
|
|
| |
added all the telnet options known to arpa/telnet.h
added all the options registered with IANA as of today
added the possibility for the user to have it's own option negotiation callback
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch is similar to that proposed by Jeremy. The proposed patch altered
the interface of TestResult such that it would be passed the error
information as a string rather than an exc_info() tuple.
The implemented change leaves the interface untouched so that TestResults
are still passed the tracebacks, but stor them in stringified form for
later reporting.
Notes:
- Custom subclasses of TestResult written by users should be unaffected.
- The existing 'unittestgui.py' will still work with this module after the
change.
- Support can later be added to pop into the debugger when an error occurs;
this support should be added to a TestRunner rather than to TestCase itself,
which this change will enable.
(Jeremy, Fred, Guido: Thanks for all the feedback)
|
| |
|
|
|
|
|
|
|
|
|
| |
1. That seeking beyond the end of a file increases the size of a file.
2. That files so extended are magically filled with null bytes.
I find no support for either in the C std, and #2 in particular turns out
not to be true on Win32 (you apparently see whatever trash happened to be
on disk). Left #1 intact, but changed the test to check only bytes it
explicitly wrote. Also fiddled the "expected" vs "got" failure reports
to consistently use repr (%r) -- they weren't readable otherwise.
|
| |
|
|
|
|
|
|
|
| |
Curious: the MS docs say stati64 etc are supported even on Win95, but
Win95 doesn't support a filesystem that allows partitions > 2 Gb.
test_largefile: This was opening its test file in text mode. I have no
idea how that worked under Win64, but it sure needs binary mode on Win98.
BTW, on Win98 test_largefile runs quickly (under a second).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requires that errno ever get set, and it looks like glibc is already
playing that game. New rules:
+ Never use HUGE_VAL. Use the new Py_HUGE_VAL instead.
+ Never believe errno. If overflow is the only thing you're interested in,
use the new Py_OVERFLOWED(x) macro. If you're interested in any libm
errors, use the new Py_SET_ERANGE_IF_OVERFLOW(x) macro, which attempts
to set errno the way C89 said it worked.
Unfortunately, none of these are reliable, but they work on Windows and I
*expect* under glibc too.
|
| |
|
|
|
|
| |
32 characters per component. This makes mkdir() calls and such fail with EINVAL.
For now I am disabling the test on the Mac, and I'll open a bugreport.
|
| |
|
|
|
|
| |
that provide a somewhat more uniform interface to getting values.
This is from SF patch #453691.
|
| |
|
|
| |
Fix up docstring for itemconfigure.
|
| |
|
|
|
| |
Patch by Jim Ahlstrom which lets java's zipfile classes read zipfiles
create by zipfile.py.
|
| | |
|
| | |
|
| |
|
|
| |
UnixWare 7.x systems.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
bdist_wininst doesn't use the NT SCHEME any more, instead
a custom SCHEME is used, which is exchanged at installation
time, depending on the python version used.
Avoid a bogus warning frpom install_lib about installing
into a directory not on sys.path.
|
| |
|
|
|
| |
This will have to stay until we decide to drop 1.5.2 compatibility
completely.
|
| |
|
|
| |
incomplete coverage of the test suite).
|
| |
|
|
| |
a default repr() that's longer than 20 characters.
|
| |
|
|
|
|
| |
getting Infs, NaNs, or nonsense in 2.1 and before; in yesterday's CVS we
were getting OverflowError; but these functions always make good sense
for positive arguments, no matter how large).
|
| |
|
|
| |
Slightly modified version of patch from Jon Nelson (jnelson).
|
| |
|
|
|
| |
INSTALLED_FILES output. Modified version of a patch from
Jon Nelson (jnelson)
|
| |
|
|
|
|
| |
"/" and "//", and doesn't really care what they *mean*, just that both
are tried (and that, whatever they mean, they act similarly for int and
long arguments).
|
| |
|
|
| |
This closes SF patch #451538.
|
| | |
|
| |
|
|
|
| |
mostly changes of / operators into //. Once or twice I did more or
less than recommended.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
change their basic behavior: When parsing something that cannot possibly
be valid in either HTML or XHTML, raise an exception.
|
| |
|
|
|
| |
the -Qwarnall option, so I've changed this to only filter out the one
warning that's a problem in practice.
|
| | |
|
| |
|
|
| |
broken declaration-like things.
|
| |
|
|
| |
regarding bare ampersands in content.
|
| |
|
|
| |
Fixed.
|
| | |
|
| | |
|
| |
|
|
| |
e.g., (1L << 40000)/(1L << 40001) returns 0.5, not Inf or NaN or whatever.
|