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 gvanrossum
Recipients gvanrossum, ncoghlan, serhiy.storchaka, taleinat
Date 2018-09-11.22:09:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536703788.56.0.0269046726804.issue32055@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that it would be less confusing if `in`/`not in` did not allow chaining, the occasional (surely very rare) useful example notwithstanding.

Then again if we're going to forbid (or even discourage) unusual combinations we might also want to frown at `a < b > c` -- surely in mathematical circles the chaining always goes in one direction only, e.g. `a < b <= c` or `a >= b ==c > d`.

Finally as long as we're refining the terminology, maybe we could strive to distinguish "comparison" (`==` and `!=`) from "ordering" (`<`, `<=`, `>`, `>=`)?
History
Date User Action Args
2018-09-11 22:09:48gvanrossumsetrecipients: + gvanrossum, ncoghlan, taleinat, serhiy.storchaka
2018-09-11 22:09:48gvanrossumsetmessageid: <1536703788.56.0.0269046726804.issue32055@psf.upfronthosting.co.za>
2018-09-11 22:09:48gvanrossumlinkissue32055 messages
2018-09-11 22:09:48gvanrossumcreate