From: "Neal Norwitz" <neal@metaslash.com> > One thing to note, many people are saying you can currently do: > > cond and true_value or false_value > > However, many have gotten it wrong, either by reversing the true/false > value or by using something in the true_value which may be false > (sometimes even constants). pychecker tries to find this condition > (when true_value is a false constant), but it does a poor job > of determining the idiom IIRC. that's why the real one (if any) should be spelled cond and! true_val or! false_val <.5 wink>. Sorry I couldn't resist.
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