python 2.3 as installed by default in MacOS X 10.3.7

This may be the same as item 991196, but that's my uneducated 
guess since I don't understand the cause of either one... (in fact it 
may not even really be a bug, but at the least this is behaviour I'm 
unable to explain).

It seems that fewer symbols are available to eval() than are 
available to literal code. The best way to describe the problem is 
with the attached short example file.

In the function evalfunction2(), a call via eval() is unable to 
resolve the symbol name evalfunction1 - even though it would be 
possible to call evalfunction1() directly.

But if the code *does* call evalfunction1() directly, then the eval() 
can see that symbol too(!).