| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
checks.
|
|
|
|
| |
compatibility layer as well as "classic" ndbm.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reverse() didn't work at all due to bad arg check.
Fixed that.
Added Brad Chapman to ACKS file, as the proud new owner of two
implicitly copyrighted lines of Python source code <wink>.
Repaired buffer_info's total lack of arg-checking.
Replaced memmove by memcpy in reverse() guts, as memmove is
often slower and the memory areas are guaranteed disjoint.
Replaced poke-and-hope unchecked decl of tmp buffer size by
assert-checked larger tmp buffer.
Got rid of inconsistent spaces before open paren in docstrings.
Added reverse() sanity tests to test_array.py.
|
|
|
|
| |
- document some of the tricky tests (hopefully correctly :)
|
|
|
|
|
|
| |
query string
also some doc string reformatting and use of string methods instead of
older string.splitfields
|
|
|
|
|
|
|
|
|
|
|
| |
Strings are unpickled by calling eval on the string's repr. This
change makes pickle work like cPickle; it checks if the pickled
string is safe to eval and raises ValueError if it is not.
test suite modifications:
Verify that pickle catches a variety of insecure string pickles
Make test_pickle and test_cpickle use exactly the same test suite
Add test for pickling recursive object
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
character according to RFC 2396. Add some text to quote doc string
that explains the quoting rules better.
This closes SF Bug #114427.
Add _fast_quote operation that uses a dictionary instead of a list
when the standard set of safe characters is used.
|
|
|
|
| |
various illegal uses of "continue".
|
|
|
|
|
|
|
|
|
|
|
| |
waste an hour tracking down an illusion; repaired it; writing/reading non-
printable characters (except \t\r\n) into/outof text-mode files ain't
defined x-platform, and at least some Windows text editors do surprising
things in their presence.
Also added a by-hand "build humber" to the Windows build, in an approximation
of Python's inexplicable BUILD-number Unix scheme. I'll try to remember to
increment it each time I make a Windows installer available. It's starting
at 2, cuz I've put 2 installers out so far (both with BUILD #0).
|
| |
|
|
|
|
|
|
|
|
|
| |
This was a funny one! The test very subtly relied on 1.5.2's
behavior of treating "\x%" as "\x%", i.e. ignoring that was an
\x escape that didn't make sense. But /F implemented PEP 223,
which causes 2.0 to raise an exception on the bad escape.
Fixed by merely making the 3 such strings of this kind into
raw strings.
|
|
|
|
| |
None (as documented) from start/end/span. closes bug #113254
|
|
|
|
|
| |
-- improved the SRE test harness: don't use asserts, test a few more
things (including more boundary conditions)
|
|
|
|
|
|
|
|
| |
newlines at the start or end. Fiddle test_popen2 and popen2._test() to
tolerate this. Also change all "assert"s in these tests to raise
explicit exceptions, so that python -O doesn't render them useless.
Also, in case of error, make the msg display the reprs of what we
wrote and what we read, so we can tell exactly why it's failing.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python test suite. Specifically,
- import time instead of strop in test_b1
- test for ClassType of exceptions using isinstance instead of
equality in test_exceptions
- remove __builtins__ from dir() output in test_pkg
test_pkg output needs to be regenerated.
|
|
|
|
| |
I fixed the a bug in the regression test harness...)
|
| |
|
|
|
|
|
|
| |
applies patch #101369 by Moshe Zadke
use explicit list of always safe characters instead of string.letters
add test case
|
|
|
|
| |
class-based APIs.
|
|
|
|
|
|
|
| |
In test_poll1(), unregister file descriptors as they're closed,
and also close the read end of the pipe
In test_poll2(), make the code assume less about the combinations of flag
bits that will be returned
|
|
|
|
| |
-- tg@FreeBSD.org
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Again due to the duplicate copies of test_support, the checked-in
"expected output" file actually contains verbose-mode output.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
subtle breakage on Windows (the test is skipped here, but the TestSkipped
exception wasn't recognized as such, because of duplicate copies of
test_support got loaded; so the test looks like a failure under Windows
instead of a skip).
Repaired the import, but
THIS TEST *WILL* FAIL ON OTHER SYSTEMS NOW!
Again due to the duplicate copies of test_support, the checked-in
"expected output" file actually contains verbose-mode output. I can't
generate the *correct* non-verbose output on my system. So, somebody
please do that.
|
|
|
|
| |
Add some test cases.
|
| |
|
|
|
|
|
| |
to be extended somewhat -- right now it only tests the .writelines()
method.
|
| |
|
|
|
|
| |
useless. So the test of the dcgettext() function is removed.
|
|
|
|
|
| |
cvs tree. It creates the directory and gettext.mo file on the fly,
from the base64 encode binary data.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
rfc822 (Addresslist) modules. Also a preliminary testcase for augmented
assignment, which should actually be merged with the test_class testcase I
added last week.
|
|
|
|
| |
fields with quoted values (as in Path="/acme")
|
|
|
|
|
|
|
| |
Update the test suite for the changes introduced by the EXTENDED_ARG
opcode.
This closes the regression test changes of SourceForge patch #100893.
|
| |
|
|
|
|
| |
name and the ":" that separates it from the value. (Minor cleanup.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
In README: Write up (Guido's) rules for intra-test imports; warn against
asserts; document test_support.use_large_resources.
|
| |
|