Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience.
...bool, True, False - these were introduced as ints in Python 2.2.1, but are now a separate type (a subtype of int). This means that True and False are now printed as the strings 'True' and 'False', respectively. As of 2.3b1, bool() without arguments returns False. (PEP 285) compile(), eval(), exec - fully support Unicode, and no longer issue a SyntaxError when their input doesn't end with a newline. (New in 2.3a2.) range() - as of 2.3b1 supports long arguments with a magnitude larger than sys....
...bool>" optional argument seems utterly application-specific. I would like to reject this because it doesn't solve a general enough problem in a general enough way, it just clutters the dictionary API. I'd rather add dict.popitem(key). PEP 266 - Optimizing Global Variable/Attribute Access Montanaro PEP 267 - Optimized Access to Module Namespaces - Hylton PEP 280 - Optimizing access to globals - van Rossum These three should be considered together; at most one of them can be impl...
...bool, has been added, as well as built-in names for its two values, True and False. Comparisons and sundry other operations that return a truth value have been changed to return a bool instead. Read PEP 285 for an explanation of why this is backward compatible. Fixed two bugs reported as SF #535905: under certain conditions, deallocating a deeply nested structure could cause a segfault in the garbage collector, due to interaction with the "trashcan" code; access to the current frame...
If you didn't find what you need, try your search in the Python language documentation.