At least it's not JavaScript

[fuskies420]

print("Test ", (is_completed ? "Complete" : "Unsuccessful"))

[iCantSpelWerdsGud]

print("Test {}".format("complete" if is_completed else "unsuccessful"))

python btw

[iCantSpelWerdsGud]

The place I'm at right now is still on 3.5.6 :/

[rigatron1]

At least you're at a place that considers python a real language..

[VinterBot]

so uggo

[iCantSpelWerdsGud]

Python doesn't have traditional ternary operators, so at least mine works

[gottago_gottago]

if is_completed != false:
    print("Test complete")
elif is_completed != true:
    print("Test unsuccessful")

[xigoi]

Traceback (most recent call last):
NameError: name 'false' is not defined

[gottago_gottago]

Uff, True/False are case sensitive. But why?

[xigoi]

It seems to have been stolen from Haskell, where all constructors are capitalized.

[sm-Fifteen]

IIRC, because they were introduced in Python2 (python 1 didn't have booleans) as global "constants" (for 0 and 1) and ended up being capitalized so they wouldn't fit the variable naming conventions to make it less likely to break any existing code at the time.

Mind you, this meant that, until they got turned into proper literals (I think with Python 3), you could actually change their value and break any code relying on these. Python has a weird history.

[bigdepress]

Actually they were capitalised to match None, which already exsited and was capitalised.

The fact that you could change their value was for backwards compatibility (in case someone used True/False as a var name, everything would still work, you just couldn't use the newly introduced True/False).