Guido van Rossum wrote: > Well, then perhaps code object comparison (and function object > comparison) ought to work the same as 'is', not try to do something > clever? This would be ironic since that's what it *used* to do long > ago, and then I thought it would be "better" if "equivalent" code > objects compared equal. It seems that there are no real use cases for > having a code object equivalence test, so we might as well save the > effort. Right? +1 (that's of course what I meant by identity comparison). Were there any use cases you thought of when you made the change? Tim Delaney
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