cpython/Lib/test/test_structseq.py

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
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!). 2001-10-30 19:20:46 -04:00			`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])`

Huh. In an effort to be less thorough <wink>, seems I checked in a new test that wouldn't even compile, 2001-10-30 23:46:14 -04:00			`# XXX more needed`