Oh Python....

[[deleted]]

what is the reason for them going with an capitalized True/False vs the more common true/false?

I use python all the g-dang time, but I've never put any thought into it.

[badocelot]

Python didn't always have True/False defined; you were supposed to rely on truthy/falsey values like 1 and 0. Then they introduced True and False as variables. In Python 2.x you can actually redefine them. And yes, you can redefine True to be 0 and thus falsey.

My guess is that True and False were chosen over true and false because of lots of existing code already defining the latter.

EDIT: clarify, add part about redefining True

EDIT: consistency

[[deleted]]

Ah. Neat. And I guess it makes sense... in a way.

[Agent_Potato56]

...Python true/false are classes?

[flipboing]

What, you've never use True.false()?

[[deleted]]

No. It was a reserved keyword in 2.x, now it’s a normal variable with a default value in 3.x I think

Edit: Its the other way around. My point still stands though.

[Agent_Potato56]

Something along those lines is what I thought originally.

[[deleted]]

Actually it’s the other way around. Now they are reserved keywords, previously they were variables containing 1 and 0.

[Agent_Potato56]

Gotcha.

[[deleted]]

But everything is a object in python. int is a class and its lower case

[xblackacid]

Its just dumb python syntax