[Guido] > Modified Files: > object.c > Log Message: > Implement the intention of SF patch 472523 (but coded differently). > > In the past, an object's tp_compare could return any value. In 2.2 > the docs were tightened to require it to return -1, 0 or 1; and -1 for > an error. > > We now issue a warning if the value is not in this range. > ... > > I haven't decided yet whether to backport this to 2.2.x. The patch > applies fine. But is it fair to start warning in 2.2.2 about code > that worked flawlessly in 2.2.1? If 2.2.x is the Python-in-a-Tie line, I say "no way". People wearing ties don't care whether a thing is right or wrong, so long as "it works" they simply don't want to hear about it at all. Converting old extensions to avoid new warnings is a 2.3 task for them.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4