All members of a camel, right? Why is True / False, but not true / false, which is more relaxed?
From Pep 285 :
Should the constants be called True, and False (similar to None) or true and false (as in C ++, Java, and C99)?=> Truth and falsehood.Most reviewers agree that consistency in Python is more important than consistency with other languages.
Should the constants be called True, and False (similar to None) or true and false (as in C ++, Java, and C99)?
=> Truth and falsehood.
Most reviewers agree that consistency in Python is more important than consistency with other languages.
Is this, as Andrew points out, perhaps because of everything (the majority)? built-in constants are capitalized .
All python inline constants are either CamelCase uppercase or [upper]:
Here's a possible explanation :
I can see that the naming conventions are such that classes usually get CamelCase names. So why are built-in types called all lowercase (e.g. list, dict, set, bool, etc.)?Since most of them were originally factory types and functions, notclasses - and naming conventions are not a strong reason to make backward incompatible changes. Different For example: a new built-in set type based on (although not quite equal to) the Set class from a set of modules
I can see that the naming conventions are such that classes usually get CamelCase names. So why are built-in types called all lowercase (e.g. list, dict, set, bool, etc.)?
Since most of them were originally factory types and functions, notclasses - and naming conventions are not a strong reason to make backward incompatible changes. Different For example: a new built-in set type based on (although not quite equal to) the Set class from a set of modules
set
I would say that they are called True and False , because they are single.
True
False
True and False capitalized in Haskell, in another language that uses indentation as syntax.