Added some tests for the truncate() method; one is commented out because

cStringIO does not get it right (reported as SF bug #115531).

Added test for ValueError when write() is called on a closed StringIO
object.  Commented out because cStringIO does not get it right
(reported as SF bug #115530).
This commit is contained in:
Fred Drake 2000-09-28 04:25:33 +00:00
parent e0a7f4f9d5
commit 954383356f
2 changed files with 25 additions and 0 deletions

View File

@ -3,7 +3,9 @@ abcdefghij
klmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
2
'abcdefghij'
abcdefghij
klmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
2
'abcdefghij'

View File

@ -9,6 +9,29 @@ def do_test(module):
print f.readline()
print len(f.readlines(60))
f = module.StringIO()
f.write(s)
f.seek(10)
f.truncate()
print `f.getvalue()`
# This test fails for cStringIO; reported as SourceForge bug #115531;
# please uncomment this test when that bug is fixed.
# http://sourceforge.net/bugs/?func=detailbug&bug_id=115531&group_id=5470
## f.seek(0)
## f.truncate(5)
## print `f.getvalue()`
# This test fails for cStringIO; reported as SourceForge bug #115530;
# please uncomment this test when that bug is fixed.
# http://sourceforge.net/bugs/?func=detailbug&bug_id=115530&group_id=5470
## try:
## f.write("frobnitz")
## except ValueError, e:
## print "Caught expected ValueError writing to closed StringIO:"
## print e
## else:
## print "Failed to catch ValueError writing to closed StringIO."
# Don't bother testing cStringIO without
import StringIO, cStringIO
do_test(StringIO)