Bill Janssen janssen at parc.com
Thu Sep 22 01:54:02 CEST 2005

• Previous message: [Python-Dev] "and" and "or" operators in Py3.0
• Next message: [Python-Dev] "and" and "or" operators in Py3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

I agree with Skip.

Bill

> 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

---

• Previous message: [Python-Dev] "and" and "or" operators in Py3.0
• Next message: [Python-Dev] "and" and "or" operators in Py3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list