What's The Difference Between "while 1" And "while True"?
Solution 1:
Fundamentally it doesn't matter, such minutiae doesn't really affect whether something is 'pythonic' or not.
If you're interested in trivia however, there are some differences.
The builtin boolean type didn't exist till Python 2.3 so code that was intended to run on ancient versions tends to use the
while 1:
form. You'll see it in the standard library, for instance.The True and False builtins are not reserved words prior to Python 3 so could be assigned to, changing their value. This helps with the case above because code could do
True = 1
for backwards compatibility, but means that the nameTrue
needs to be looked up in the globals dictionary every time it is used.Because of the above restriction, the bytecode the two versions compile to is different in Python 2 as there's an optimisation for constant integers that it can't use for
True
. Because Python can tell when compiling the1
that it's always non-zero, it removes the conditional jump and doesn't load the constant at all:>>>import dis>>>defwhile_1():...while1:...pass...>>>defwhile_true():...whileTrue:...pass...>>>dis.dis(while_1) 2 0 SETUP_LOOP 5 (to 8) 3 >> 3 JUMP_ABSOLUTE 3 6 POP_TOP 7 POP_BLOCK >> 8 LOAD_CONST 0 (None) 11 RETURN_VALUE >>>dis.dis(while_true) 2 0 SETUP_LOOP 12 (to 15) >> 3 LOAD_GLOBAL 0 (True) 6 JUMP_IF_FALSE 4 (to 13) 9 POP_TOP 3 10 JUMP_ABSOLUTE 3 >> 13 POP_TOP 14 POP_BLOCK >> 15 LOAD_CONST 0 (None) 18 RETURN_VALUE
So, while True:
is a little easier to read, and while 1:
is a bit kinder to old versions of Python. As you're unlikely to need to run on Python 2.2 these days or need to worry about the bytecode count of your loops, the former is marginally preferable.
Solution 2:
The most pythonic way will always be the most readable. Use while True:
Solution 3:
It doesn't really matter. Neither is hard to read or understand, though personally I'd always use while True
, which is a bit more explicit.
More generally, a whole lot of while–break loops people write in Python could be something else. Sometimes I see people write i = 0; while True: i += 1 ...
, which can be replaced with for i in itertools.count()
and people writing while True: foo = fun() if foo is None: break
when this can be written for foo in iter(fun, None)
, which requires learning but has less boilerplate and opportunity for silly mistakes.
Solution 4:
Neither.
Both of them mean I have to scan the code looking for the break
, instead of being able to see the stop condition right where it belongs.
I try to avoid this kind of thing wherever possible, and if it's not possible, let the code speak for itself like this:
while not found_answer:check_number+=1ifcheck_number==42:found_answer=True
Edit: It seems that the word "avoid" above wasn't clear enough. Using a basically infinite loop and leaving it from somewhere within the loop (using break
) should usually be avoided altogether. Sometimes that isn't possible. In that case, I like to use something like the code above, which, however, still represents the same concept – the above code is nothing more than a compromise – but at least, I can show the purpose of the loop at the beginning – just like I wouldn't call a function do_something_with_args(*args)
.
Solution 5:
IMO the second option is more obvious.
If you could get rid of the while
and write more compact code, that might be more pythonic.
For example:
# Get the even numbers in the range 1..10# Version 1
l = []
n = 1while1:
if n % 2 == 0: l.append(n)
n += 1if n > 10: breakprint l
# Version 2print [i for i inrange(1, 11) if i % 2 == 0]
# Version 3printrange(2, 11, 2)
Post a Comment for "What's The Difference Between "while 1" And "while True"?"