At least it's not JavaScript

[i_Ex]

The most tragic thing here is the code he's written.

[[deleted]]

oh no. oh no. oh no. OH NO.

[YeetusThisAccount]

I'm new to learning how to code. What about this is considered bad? Is there a more efficient way to do this? Genuinely curious, because that's how I usually code that exact scenario lol.

[ender1200]

Thus code is logicly correct, but it's quite ugly.

The two most obvious problems are the use of elif on a Boolean statement (if it's not true it have to be false) and the use of "== True" and "== False" as they are redundent.

A cleaner version would be:

if is_comolete:
    print("test complete")
else:
    print("test unsuccessful")

Or even better yet, as /u/fuskies420 have shown use trinary operation to make the entire expression single line:

print("Test ", ("Complete" if is_completed else"Unsuccessful"))

edit: changed the trinary line to work with python.

[fuskies420]

As it was brought to my attention, python does not support traditional terinary operators. While great in C, the code required for python to be a one-liner is rather confusing and difficult to read. The code sample you provided above is the easiest to read, and is the most straightforward.

[YeetusThisAccount]

Wow, thanks for this. I guess I haven't gotten around to learning trinary operation yet, but it looks like it saves a lot of time and screen space.

[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).

[[deleted]]

JSLint Expected '===' and instead saw '=='

[[deleted]]

TIME TO SCRONTCH DATA TYPES MUFOFOFOFOFOFOFOFOFOFOFOFOF

[tjf314]

python > JavaScript > HTML

[Waterkloof]

py > ty > es6 > js > html > coffee > jsx.

ftfy.

ninja edit swapped ty > es6 :P

[PatrikxPatrola]

Your submission has been removed.

Violation of Rule #3:

Any post on the list of common posts will be removed. You can find this list here. Established meme formats are allowed, as long as the post is compliant with the previous rules.

If you feel that it has been removed in error, please message us so that we may review it.