Fiddle with new test cases -- verify that we get a sensible error

message for bad mode argument -- so that it doesn't fail on Windows.

It's hack.  We know that errno is set to 0 in this case on Windows, so
check for that specifically.
This commit is contained in:
Jeremy Hylton 2001-11-09 19:34:43 +00:00
parent a4e5c71962
commit 734c7fb131
1 changed files with 7 additions and 4 deletions

View File

@ -46,14 +46,17 @@ else:
print "writelines accepted sequence of non-string objects" print "writelines accepted sequence of non-string objects"
f.close() f.close()
# verify that we get a sensible error message for bad made argument # verify that we get a sensible error message for bad mode argument
bad_mode = "qwerty" bad_mode = "qwerty"
try: try:
open(TESTFN, bad_mode) open(TESTFN, bad_mode)
except IOError, msg: except IOError, msg:
s = str(msg) if msg[0] != 0:
if s.find(TESTFN) != -1 or s.find(bad_mode) == -1: s = str(msg)
print "bad error message for invalid mode: %s" % s if s.find(TESTFN) != -1 or s.find(bad_mode) == -1:
print "bad error message for invalid mode: %s" % s
# if msg[0] == 0, we're probably on Windows where there may be
# no obvious way to discover why open() failed.
else: else:
print "no error for invalid mode: %s" % bad_mode print "no error for invalid mode: %s" % bad_mode