name capitalization of built-in types, True, and False

[cbtube03]

I see that naming conventions are such that classes usually get named
CamelCase. So why are the built-in types named all lowercase (like
list, dict, set, bool, etc.)?

And names for instances of classes are usually written in lowercase,
like foo in ``foo = CamelCase()``. So why are True and False
(instances of bool) capitalized? Shouldn't they be "true" and "false"?
Same goes for None.

 

[James Stroud]

I see that naming conventions are such that classes usually get named
CamelCase. So why are the built-in types named all lowercase (like
list, dict, set, bool, etc.)?

And names for instances of classes are usually written in lowercase,
like foo in ``foo = CamelCase()``. So why are True and False
(instances of bool) capitalized? Shouldn't they be "true" and "false"?
Same goes for None.

My guess is that TRUE, FALSE, and NONE are fairly unbecoming and all
lowercase would not do justice to their status as language constants.

 

[Gabriel Genellina]

I see that naming conventions are such that classes usually get named
CamelCase. So why are the built-in types named all lowercase (like
list, dict, set, bool, etc.)?

Because most of them originally were types and factory functions, not
classes - and a naming convention is not a strong reason to make backwards
incompatible changes.
A different example: the new builtin type `set` is based on (altough not
exactly equal to) the Set class from the sets module