summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_cpickle.py
Commit message (Collapse)AuthorAgeFilesLines
* Getting rid of cPickle. Mmm, feels good!Guido van Rossum2007-07-201-103/+0
|
* Use absolute import. (Should this go into 2.5?)Neal Norwitz2006-03-241-1/+1
|
* Combine the functionality of test_support.run_unittest()Walter Dörwald2003-05-011-7/+6
| | | | | | | | | | and test_support.run_classtests() into run_unittest() and use it wherever possible. Also don't use "from test.test_support import ...", but "from test import test_support" in a few spots. From SF patch #662807.
* SF bug 690622: test_cpickle overflows stack on MacOS9.Tim Peters2003-02-211-1/+5
| | | | | | | | test_nonrecursive_deep(): Reduced nesting depth to 60. Not a bugfix candidate. 2.3 increased the number of stack frames needed to pickle a list (in order to get implement the "list batching" unpickling memory optimization new in 2.3).
* Renamed "bin" arguments to "proto". Note that this test currentlyTim Peters2003-01-281-6/+6
| | | | fails, for reasons unrelated to this patch.
* Get rid of relative imports in all unittests. Now anything thatBarry Warsaw2002-07-231-1/+1
| | | | | | | | | | | imports e.g. test_support must do so using an absolute package name such as "import test.test_support" or "from test import test_support". This also updates the README in Lib/test, and gets rid of the duplicate data dirctory in Lib/test/data (replaced by Lib/email/test/data). Now Tim and Jack can have at it. :)
* Merge of the release22 branch changes back into the trunk.Barry Warsaw2001-12-211-0/+7
|
* Fix the test control support for the pickle & cPickle tests so the tests runFred Drake2001-12-191-5/+12
| | | | under regrtest.
* Whitespace normalization.Tim Peters2001-10-181-1/+1
|
* Covert pickle tests to use unittest.Jeremy Hylton2001-10-151-2/+85
| | | | | Extend tests to cover a few more cases. For cPickle, test several of the undocumented features.
* Reorganize pickle/cPickle testing so the tests pass regardless of the orderTim Peters2001-01-221-4/+2
| | | | they're run.
* Fix Bug #114293:Jeremy Hylton2000-09-151-104/+2
| | | | | | | | | | | Strings are unpickled by calling eval on the string's repr. This change makes pickle work like cPickle; it checks if the pickled string is safe to eval and raises ValueError if it is not. test suite modifications: Verify that pickle catches a variety of insecure string pickles Make test_pickle and test_cpickle use exactly the same test suite Add test for pickling recursive object
* Charles Waldman writes:Guido van Rossum2000-04-211-4/+4
| | | | | | | | | | """ 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. """
* Add test case for bug just fixed by Stephen Turner.Guido van Rossum1999-07-131-0/+11
|
* Jonathan Giddy write:Guido van Rossum1999-04-011-0/+1
| | | | | In test_cpickle.py, the module os got imported, but the line to remove the temp file has gone missing.
* Test protection against picling to/from closed (real) file.Guido van Rossum1999-03-291-0/+20
|
* Basic regr tests for pickle/cPickleGuido van Rossum1999-03-251-0/+75