On 8/10/06, Michael Urman <murman at gmail.com> wrote: > I strongly believe that unicode vs str here is the symptom and not the > actual problem. No. Everywhere when __eq__ fails, we can safely tell the user that it's a bug in their __eq__ that they should fix (maybe by making it return False when the other object isn't a type they recognize). But we can't fix unicode-vs-str comparison without breaking too much code. So we have to somehow deal with that without changing the behavior of that particular __eq__. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
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