8 Apr
2016
8 Apr
'16
8:57 p.m.
On Fri, Apr 8, 2016, at 11:00, Guido van Rossum wrote:
The thing here is, this change is too small to warrant a __future__ import. So we're either going to introduce it in 3.6 and tell people about it in case their code might break, or we're never going to do it. I'm honestly on the fence, but I feel this is a rarely used operator so changing its meaning is not likely to break a lot of code.
What about just having a DeprecationWarning, but no __future__ import?