[issue11477] Incorrect operand precedence when implementing sequences in C

[Gregory P. Smith]

Gregory P. Smith <greg at krypto.org> added the comment:

Given that a lot of code is presumably relying on this (see the notes from 2015)... I wouldn't be surprised if this turns into a wart we document but not actually fix. :/

Or a conditional behavior we control via a `from __future__ import correct_extension_operator_precedence` on a per file / per Notebook basis.

Ever actually flipping the default sounds difficult without disruption.  We'd need input from the community where extensions that rely on it have been produced and widely deployed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue11477>
_______________________________________