diff options
| author | Tim Peters <tim.peters@gmail.com> | 2001-10-30 23:20:46 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2001-10-30 23:20:46 (GMT) |
| commit | c2fe618575aaf58ddf36d04d96431d6dc819ef31 (patch) | |
| tree | f083f6119e71555915d02a04de993e97d7d36ffc /Lib/test/test_structseq.py | |
| parent | 5ded1bf5c7773b7a13e1907e3cfb4826c402d7b2 (diff) | |
| download | cpython-c2fe618575aaf58ddf36d04d96431d6dc819ef31.zip cpython-c2fe618575aaf58ddf36d04d96431d6dc819ef31.tar.gz cpython-c2fe618575aaf58ddf36d04d96431d6dc819ef31.tar.bz2 | |
Fix bad bug in structseq slicing (NULL pointers in result). Reported by
Jack Jansen on python-dev.
Add simple test case.
Move vereq() from test_descr to test_support (it's handy!).
Diffstat (limited to 'Lib/test/test_structseq.py')
| -rw-r--r-- | Lib/test/test_structseq.py | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/Lib/test/test_structseq.py b/Lib/test/test_structseq.py new file mode 100644 index 0000000..33d3313 --- /dev/null +++ b/Lib/test/test_structseq.py @@ -0,0 +1,16 @@ +from test_support import vereq + +import time + +t = time.gmtime() +astuple = tuple(t) +vereq(len(t), len(astuple)) +vereq(t, astuple) + +# Check that slicing works the same way; at one point, slicing t[i:j] with +# 0 < i < j could produce NULLs in the result. +for i in range(-len(t), len(t)): + for j in range(-len(t), len(t)): + vereq(t[i:j], astuple[i:j]) + +XXX more needed |