[SciPy-dev] Backwards compatibility for weave
eric at scipy.org
Tue Apr 23 13:16:53 CDT 2002
I haven't tested weave against Python 2.0. The _getframe work around suggested
by Pearu might help. Also, I think the standard inspect.py module has a stack()
function that serves a similar function. I'm not sure if inspect.py was part of
2.0 though. weave also needs distutils -- I think it was in 2.0, right?
Other than that, I don't know of any other show stoppers. The code generator is
all pure Python code that, other than the stack shinanigans, doesn't do anything
too strange. Since it uses distutils, weave should build the extension modules
with all the correct settings for 2.0 automatically.
Let me know if there are some easy fixes. I'm loath to give up the _getframe
call because it is much more efficient than other approaches. Extra checks and
function calls within inline() or blitz() come at a high price because they slow
down every call to a compiled function. However, we could supply a different
version of the functions that work with 2.0 if the fixes are simple.
----- Original Message -----
From: "David O'Gwynn" <dog at ERC.MsState.Edu>
To: <scipy-dev at scipy.org>
Sent: Tuesday, April 23, 2002 7:32 AM
Subject: [SciPy-dev] Backwards compatibility for weave
> In trying to use weave on the system where I work, I found that it will
> not work with Python2.0. Namely because of the use of the sys._getframe
> method. There might be other compatibility issues as well.
> Is there any kind of workaround for backwards compatibility?
> David O'Gwynn
> dog at erc.msstate.edu
> Scipy-dev mailing list
> Scipy-dev at scipy.net
More information about the Scipy-dev