DeprecationWarning every time you use ~ on a bool? That would still be
too big a burden on using it the new way.
I think proposal would be a DeprecationWarning to flush out/remove all current uses of ~bool with Python 3.6, and then in Python 3.7 introduce the new semantics.
-Brett
On Fri, Apr 8, 2016 at 8:27 AM, Random832 <random832@fastmail.com> wrote:
>
>
> 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?
> _______________________________________________
> Python-ideas mailing list
> Python-ideas@python.org
> https://mail.python.org/mailman/listinfo/python-ideas
> Code of Conduct: http://python.org/psf/codeofconduct/
--
--Guido van Rossum (python.org/~guido)
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/