summaryrefslogtreecommitdiffstats
path: root/Lib/test/mapping_tests.py
Commit message (Collapse)AuthorAgeFilesLines
* Merge from 3.1: Issue #13703: add a way to randomize the hash values of ↵Georg Brandl2012-02-201-1/+1
|\ | | | | | | | | | | | | | | | | basic types (str, bytes, datetime) in order to make algorithmic complexity attacks on (e.g.) web apps much more complicated. The environment variable PYTHONHASHSEED and the new command line flag -R control this behavior.
| * Issue #13703: add a way to randomize the hash values of basic types (str, ↵Georg Brandl2012-02-201-1/+1
| | | | | | | | | | | | | | | | | | bytes, datetime) in order to make algorithmic complexity attacks on (e.g.) web apps much more complicated. The environment variable PYTHONHASHSEED and the new command line flag -R control this behavior.
| * Merged revisions 73715 via svnmerge fromGeorg Brandl2009-08-131-46/+46
| | | | | | | | | | | | | | | | | | | | svn+ssh://svn.python.org/python/branches/py3k ........ r73715 | benjamin.peterson | 2009-07-01 01:06:06 +0200 (Mi, 01 Jul 2009) | 1 line convert old fail* assertions to assert* ........
* | Merged revisions 77727 via svnmerge fromEzio Melotti2010-01-241-6/+4
| | | | | | | | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r77727 | ezio.melotti | 2010-01-24 18:58:36 +0200 (Sun, 24 Jan 2010) | 1 line use assert[Not]IsInstance where appropriate ........
* | use assert[Not]In where appropriateEzio Melotti2010-01-231-14/+15
| |
* | Issue #7435: Remove duplicate int/long tests, and otherMark Dickinson2009-12-051-7/+0
| | | | | | | | references to long in py3k. Patch provided by flox.
* | convert old fail* assertions to assert*Benjamin Peterson2009-06-301-46/+46
|/
* Migrate remaining tests from UserDict.UserDict to collections.UserDict.Raymond Hettinger2008-02-061-5/+5
|
* PEP 3114: rename .next() to .__next__() and add next() builtin.Georg Brandl2007-04-211-9/+9
|
* Fix test_os from breakage due to dict views.Brett Cannon2007-02-211-1/+1
|
* Fix the damage to UserDict and its tests.Guido van Rossum2007-02-151-3/+3
| | | | | | | Clearly this is not the right way to fix this; UserDict and MixinDict ought to be redesigned with the new dict API in mind. But I'm not claiming to be in charge of library redesign, I only want zero failing tests.
* Nailed test_weakref.py. Pfew, messy!Guido van Rossum2007-02-111-30/+34
|
* - PEP 3106: dict.iterkeys(), .iteritems(), .itervalues() are now gone;Guido van Rossum2007-02-111-9/+9
| | | | | | | | | | and .keys(), .items(), .values() return dict views. The dict views aren't fully functional yet; in particular, they can't be compared to sets yet. but they are useful as "iterator wells". There are still 27 failing unit tests; I expect that many of these have fairly trivial fixes, but there are so many, I could use help.
* Rip out 'long' and 'L'-suffixed integer literals.Guido van Rossum2007-01-151-2/+2
| | | | (Rough first cut.)
* Restructure comparison dramatically. There is no longer a defaultGuido van Rossum2006-08-241-14/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | *ordering* between objects; there is only a default equality test (defined by an object being equal to itself only). Read the comment in object.c. The current implementation never uses a three-way comparison to compute a rich comparison, but it does use a rich comparison to compute a three-way comparison. I'm not quite done ripping out all the calls to PyObject_Compare/Cmp, or replacing tp_compare implementations with tp_richcompare implementations; but much of that has happened (to make most unit tests pass). The following tests still fail, because I need help deciding or understanding: test_codeop -- depends on comparing code objects test_datetime -- need Tim Peters' opinion test_marshal -- depends on comparing code objects test_mutants -- need help understanding it The problem with test_codeop and test_marshal is this: these tests compare two different code objects and expect them to be equal. Is that still a feature we'd like to support? I've temporarily removed the comparison and hash code from code objects, so they use the default (equality by pointer only) comparison. For the other two tests, run them to see for yourself. (There may be more failing test with "-u all".) A general problem with getting lots of these tests to pass is the reality that for object types that have a natural total ordering, implementing __cmp__ is much more convenient than implementing __eq__, __ne__, __lt__, and so on. Should we go back to allowing __cmp__ to provide a total ordering? Should we provide some other way to implement rich comparison with a single method override? Alex proposed a __key__() method; I've considered a __richcmp__() method. Or perhaps __cmp__() just shouldn't be killed off...
* Change the way __hash__ is inherited; when __eq__ or __cmp__ is overriddenGuido van Rossum2006-08-211-0/+4
| | | | | but __hash__ is not, set __hash__ explicitly to None (and tp_hash to NULL). All unit tests pass now!
* Get rid of dict.has_key(). Boy this has a lot of repercussions!Guido van Rossum2006-08-181-13/+1
| | | | | | Not all code has been fixed yet; this is just a checkpoint... The C API still has PyDict_HasKey() and _HasKeyString(); not sure if I want to change those just yet.
* Rename class attribute containing the class to be tested, so the name is theWalter Dörwald2004-06-021-10/+10
| | | | same as for the string and sequence tests.
* Port the dictionary tests from test_types.py to unittest. Collect as muchWalter Dörwald2004-05-311-0/+672
mapping tests as possible in mapping_test.py and reuse the tests in test_dict.py, test_userdict.py, test_weakref.py, test_os.py and test_shelve.py. From SF patch #736962.
generated by cgit v0.12 at 2024-12-04 19:58:13 (GMT)