[issue27754] Changing the meaning of bool.__invert__

Changes by Benjamin Peterson : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue27754] Changing the meaning of bool.__invert__

Raymond Hettinger added the comment: >>> ... it would be nice if ~ acted as negation on bools (~False being >>> True and ~True being false) instead of mapping them to -1 and -2 >>> as it currently does. I'm strongly against this proposal for several reasons. 1. One way to do it. We don't need

[issue27754] Changing the meaning of bool.__invert__

R. David Murray added the comment: Well, maybe I'm wrong about the 'next feature release' bit, I won't claim to be able to read Guido's mind :) -- ___ Python tracker ___ ___

[issue27754] Changing the meaning of bool.__invert__

R. David Murray added the comment: Well, in this context "in 3.6" means "in the next feature release", so it isn't as if the window closes forever. I'd vote -1 myself. It doesn't seem like a useful enough feature to be worth adding, given that ~x is equivalent to "not x" for booleans, but "no

[issue27754] Changing the meaning of bool.__invert__

Vedran Čačić added the comment: Ok, so let me try to summarize. Some people realized that & and | on bools are overridden to return bools instead of ints, and thought it would be nice if ~ acted as negation on bools (~False being True and ~True being false) instead of mapping them to -1 and -2

[issue27754] Changing the meaning of bool.__invert__

R. David Murray added the comment: That doesn't look like a thread consensus, nor does the link you provide explain what is under discussion. I'm not going to search the thread myself, so my answer right now is "dropped" unless there was actually a positive conclusion to that thread for whate

[issue27754] Changing the meaning of bool.__invert__

New submission from Vedran Čačić: Not that I'm very much for it, but I'd like this not to be forgotten: https://mail.python.org/pipermail/python-ideas/2016-April/039665.html Is this going to be done in Py3.6? Or officially dropped? -- messages: 272597 nosy: veky priority: normal severi