[Python-ideas] Changing the meaning of bool.__invert__
Random832
random832 at fastmail.com
Fri Apr 8 11:27:13 EDT 2016
More information about the Python-ideas mailing list
Fri Apr 8 11:27:13 EDT 2016
- Previous message (by thread): [Python-ideas] Changing the meaning of bool.__invert__
- Next message (by thread): [Python-ideas] Changing the meaning of bool.__invert__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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?
- Previous message (by thread): [Python-ideas] Changing the meaning of bool.__invert__
- Next message (by thread): [Python-ideas] Changing the meaning of bool.__invert__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list