From 84219682fbfb1aff829ed2d3f0bad42c43fc969c Mon Sep 17 00:00:00 2001 From: Guido van Rossum Date: Fri, 21 Apr 2000 20:49:58 +0000 Subject: [PATCH] Charles Waldman writes: """ In the course of debugging this I also saw that cPickle is inconsistent with pickle - if you attempt a pickle.load or pickle.dump on a closed file, you get a ValueError, whereas the corresponding cPickle operations give an IOError. Since cPickle is advertised as being compatible with pickle, I changed these exceptions to match. """ --- Lib/test/test_cpickle.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Lib/test/test_cpickle.py b/Lib/test/test_cpickle.py index 7cc4b1fccc..f5e920fd49 100644 --- a/Lib/test/test_cpickle.py +++ b/Lib/test/test_cpickle.py @@ -79,18 +79,18 @@ def dotest(): f.close() try: cPickle.dump(123, f) - except IOError: + except ValueError: pass else: - print "dump to closed file should raise IOError" + print "dump to closed file should raise ValueError" f = open(fn, "r") f.close() try: cPickle.load(f) - except IOError: + except ValueError: pass else: - print "load from closed file should raise IOError" + print "load from closed file should raise ValueError" os.remove(fn) # Test specific bad cases -- 2.40.0