Thanks Michael & Dino, That gets me a step further:
>>> from sympy import Symbol Traceback (most recent call last): File "<stdin>", line 1, in <module> File "c:\Program Files (x86)\Python26\Lib\site-packages\sympy\__init__.py", line 44, in c:\Program Files (x86)\Python26\Lib\site-packages\sympy\__init__.py NameError: global name 'evalf' is not defined >>> evalf is a module that is part of sympy.core. This works fine on CPython 2.6. I can get around the problem by commenting out the offending line, which doesn't seem to have any breaking side-effects. Still, given the performance degradation, it seems odd you have to turn frames on just to import a module regardless of whether you actually need the frames functionality. Jeffrey -----Original Message----- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland Sent: July-24-09 4:50 PM To: Discussion of IronPython Subject: Re: [IronPython] sympy on IP 2.6B2 -X:FullFrames promotes all local variables into the heap. So you can always crawl the stack and look/change them for all methods. -X:Frames only creates the frame objects and if something happens to make us promote local variables (e.g. a closure, or a call to locals(), exec, eval, dir(), vars()) then the local variables will be available for that specific method. > -----Original Message----- > From: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] On Behalf Of Michael Foord > Sent: Friday, July 24, 2009 1:47 PM > To: Discussion of IronPython > Subject: Re: [IronPython] sympy on IP 2.6B2 > > Try running it with frames switched on: > > ipy.exe -X:Frames > > or: > > ipy.exe -X:FullFrames > > Perhaps Dino can explain what the difference is between these two > modes... :-) > > Michael > _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com