- ...prompt.
-
A problem with the GNU Readline package may prevent this.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...value.
-
Actually, call by object reference would be a better
description, since if a mutable object is passed, the caller
will see any changes the callee makes to it (e.g., items
inserted into a list).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...etc.
-
The rules for comparing objects of different types should
not be relied upon; they may change in a future version of
the language.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...somewhere.
-
In fact function definitions are also `statements' that are
`executed'; the execution enters the function name in the
module's global symbol table.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...space!
-
Except for one thing. Module objects have a secret read-only
attribute called
__dict__ which returns the dictionary
used to implement the module's name space; the name
__dict__ is an attribute but not a global name.
Obviously, using this violates the abstraction of name space
implementation, and should be restricted to things like
post-mortem debuggers...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.