Guido van Rossum added the comment: > As I understand it comparisons between two objects should > always work.
Hi Aaron! Glad to see you're back. It used to be that way when you & Jim wrote the first Python book. :-) Nowadays, comparisons *can* raise exceptions. Marc-Andre has explained why. In 3.0, this particular issue will go away due to a different treatment of Unicode, but many more cases will raise TypeError when < is used. == and != will generally work, though there are no absolute guarantees. ---------- nosy: +gvanrossum resolution: -> rejected status: open -> closed __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1997> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
