A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/056612.html below:

[Python-Dev] "and" and "or" operators in Py3.0

[Python-Dev] "and" and "or" operators in Py3.0 [Python-Dev] "and" and "or" operators in Py3.0skip@pobox.com skip at pobox.com
Wed Sep 21 16:22:09 CEST 2005
I suppose this is a dead horse now, but I will kick it one more time.

Under the rubrics of "explicit is better than implicit" and "there should
only be one wat to do it", I would rather see

    bool_val = bool(foo or bar)

instead of having the "or" operator implicitly call bool() for me.  There's
clear value to the current semantics and it's so easy to get a boolean if
you want it, I see no reason for a change.

Skip
More information about the Python-Dev mailing list

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