summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_compare.py
Commit message (Collapse)AuthorAgeFilesLines
* By default, != returns the opposite of ==, unless the latter returnsGuido van Rossum2007-03-271-0/+6
| | | | | | NotImplemented. (Is this worth backporting to 2.6? It seems so useful...!)
* Rip out 'long' and 'L'-suffixed integer literals.Guido van Rossum2007-01-151-1/+1
| | | | (Rough first cut.)
* Restructure comparison dramatically. There is no longer a defaultGuido van Rossum2006-08-241-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | *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...
* __coerce__ is gone, there's nothing to test.Neal Norwitz2006-04-301-14/+1
| | | | This test now passes after removing refs to __coerce__.
* Merge p3yk branch with the trunk up to revision 45595. This breaks a fairThomas Wouters2006-04-211-23/+28
| | | | | | | | | | | | | | | | | | | | number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
* Complete the absolute import patch for the test suite. All relativeBarry Warsaw2002-07-301-2/+0
| | | | | | | | imports of test modules now import from the test package. Other related oddities are also fixed (like DeprecationWarning filters that weren't specifying the full import part, etc.). Also did a general code cleanup to remove all "from test.test_support import *"'s. Other from...import *'s weren't changed.
* The first batch of changes recommended by the fixdiv tool. These areGuido van Rossum2001-09-041-1/+1
| | | | | mostly changes of / operators into //. Once or twice I did more or less than recommended.
* Repair some accidents causing Windows failures:Tim Peters2001-08-161-1/+1
| | | | | | | + test_compare. While None compares less than anything else, it's not always the case that None has the smallest id(). + test_descr. The output of %p (pointer) formats varies across platforms. In particular, on Windows it doesn't produce a leading "0x".
* Given a class without __cmp__ or __eq__, cmp() of two instances ofGuido van Rossum2001-08-151-0/+8
| | | | | | that class should compare the id() of those instances. Add a test that verifies this. This test currently fails; I believe this is caused by object.c:2.132 (Patch #424475 by loewis).
* __rcmp__ no longer gets called on instances. Remove the test for it.Neil Schemenauer2001-01-041-12/+1
|
* Use == rather than cmp(). The return value of cmp() is not well defined whenNeil Schemenauer2001-01-031-7/+9
| | | | comparing different types.
* Add more tests for compare and coercion in preparation for the coercionNeil Schemenauer2001-01-021-0/+57
overhaul. Closes SF patch #102878.