➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients barry, benjamin.peterson, brett.cannon, docs@python, eli.bendersky, eric.araujo, fdrake, flox, ncoghlan, pitrou, python-dev
Date 2011-11-14.13:23:41
SpamBayes Score 0.00018126426
Marked as misclassified No
Message-id <1321277021.94.0.169866167348.issue13239@psf.upfronthosting.co.za>
In-reply-to
Content 
+# <> isn't actually a valid comparison operator in Python. It's here for the
+# sake of a __future__ import described in PEP 401

If we wanted to be exact, the operator isn’t here for a __future__ import but for a feature enabled by a __future__ import.  But I don’t feel strongly about this at all :)
History
Date User Action Args
2011-11-14 13:23:42eric.araujosetrecipients: + eric.araujo, fdrake, barry, brett.cannon, ncoghlan, pitrou, benjamin.peterson, eli.bendersky, flox, docs@python, python-dev
2011-11-14 13:23:41eric.araujosetmessageid: <1321277021.94.0.169866167348.issue13239@psf.upfronthosting.co.za>
2011-11-14 13:23:41eric.araujolinkissue13239 messages
2011-11-14 13:23:41eric.araujocreate