FWIW, I do the same thing every time I need to work with booleans. I try to "say what I mean" when I program, and, I'm sorry, but "return 1|0" just doesn't say "I mean to return something which will be interpreted as true|false". I want the language to help me say what I mean. I do understand about the backward-compatibility issues introduced by adding bool, but I don't understand why there are claims that there will be more than one official way to return boolean results. It seems to me that the only thing pointing to 1|0 as the right way would be legacy code, and everything in the language would point at true|false. -Dave ----- Original Message ----- From: "Mark McEahern" <marklists@mceahern.com> > [Kevin Jacobs] > > The moral of the story is that I will be extremely happy once there is a > > globally blessed way of spelling true and false other than 1 and 0. Of > > course, I and my team aren't exactly typical Python developers. Though > > wouldn't it be nice if we were? > > I'd like to consciously go out of my way and violate all rules of netiquette > and say simply this: > > Me too.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4