...made.
The interpreter should really distinguish between user-defined classes implementing sequences, mappings or numbers, but currently it doesn't --- hence this strange exception.
...raised.
If the code block contains exec statements or the construct from ...import *, the semantics of names not explicitly mentioned in a global statement change subtly: name lookup first searches the local name space, then the global one, then the built-in one.
...undefined.
The current implementations return the dictionary actually used to implement the name space, except for functions, where the optimizer may cause the local name space to be implemented differently, and locals() returns a read-only dictionary.
...arguments:
The new syntax for keyword arguments is not yet documented in this manual. See chapter 12 of the Tutorial.
...lists.
This is expensive since it requires sorting the keys first, but about the only sensible definition. An earlier version of Python compared dictionaries by identity only, but this caused surprises because people expected to be able to test a dictionary for emptiness by comparing it to {}.
...one.
The latter restriction is sometimes a nuisance.
...loop.
Except that it may currently occur within an except clause.
...#types#1189>):
The new syntax to receive arbitrary keyword arguments is not yet documented in this manual. See chapter 12 of the Tutorial.
...grammar.
Currently this is not checked; instead, def f(a=1,b) is interpreted as def f(a=1,b=None).

guido@cwi.nl