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/2002-March/020920.html below:

[Python-Dev] Boolean transition

[Python-Dev] Boolean transition [Python-Dev] Boolean transitionSamuele Pedroni pedroni@inf.ethz.ch
Mon, 11 Mar 2002 03:27:49 +0100
From: Samuele Pedroni <pedroni@inf.ethz.ch>
> 
> But as long as in Python 3000:
> if 0: ...  and if 1: ... work
> then someone can still hang himself calling it so:
> 
> foo(0,10)
> 
> Maybe it is just FUD, but the question
> whether people will adopt the change
> and apply it to old code is central.
> That means it *should* be asked, then
> you can answer FUD, but just then.
> 

That means - restated - that the only way
to take seriously and to make Paul Prescod's point 
effective is to deprecate:
 
 if <number>: ... etc

Already issuing warnings with 2.3,
because - here - the sooner the better <wink>,
or keep things more or less as they are
(Guido proposals).

Obviously we will still be able to
use lists/strings etc
in Boolean context but not 
numbers just bools.

regards.






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