mirror of
https://github.com/python/cpython.git
synced 2025-08-30 21:48:47 +00:00
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!).
This commit is contained in:
parent
5ded1bf5c7
commit
c2fe618575
4 changed files with 22 additions and 6 deletions
16
Lib/test/test_structseq.py
Normal file
16
Lib/test/test_structseq.py
Normal file
|
@ -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
|
Loading…
Add table
Add a link
Reference in a new issue