From: Maurice L. <mj...@ga...> - 2002-08-19 11:20:51
|
Just a FYI. I decided to try once again to get the python bindings to work on my RH7.3 machines. First I built & installed the latest swig, making sure it came first in my path, and then that part was traversed correctly. However more problems: 1. During the make I get: python setup.py build --force --build-temp="./" --build-lib="./" --flat Traceback (innermost last): File "setup.py", line 45, in ? libs_list = libs.split(" ") AttributeError: 'string' object has no attribute 'split' make: *** [plplotcmodule.so] Error 1 where "python" for RH7.3 is python1.5. Is python1.5 no longer supported? 2. I added the necessary search path for python2.2 to the config files. The python for python2.2 under RH7.3 is called "python2". I also found I had to build & install Numeric from tarball (no RPM is available), so I did so. Everything configured fine at that point, but the make died at the same place as #1 because the make uses "python" rather than "python2". So, I entered this command by hand, typed "make" again, and everything finally was built. 3. Tried to run the demos, and it failed. From the tmp dir: trinity$ ./pythondemos.py Traceback (innermost last): File "./pythondemos.py", line 15, in ? from plplot import * File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? from plplotc import * ImportError: /home/mjl/dev/plplot/plpy/tmp/plplotcmodule.so: undefined symbol: PySequence_Size So maybe again it was a python vs python2 problem. Trying again: trinity$ python2 ./pythondemos.py Traceback (most recent call last): File "./pythondemos.py", line 15, in ? from plplot import * File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? from plplotc import * ImportError: dynamic module does not define init function (initplplotc) Any ideas? -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Maurice L. <mj...@ga...> - 2002-08-19 11:42:21
|
Maurice LeBrun writes: > [python1.5 vs python2.2 problems] BTW a symlink from /usr/bin/python2.2 to ~/bin/python took care of all of these problems. Probably RedHat will go with python == python2.2 starting with their 8.0 release, but for now the symlink solution works fine. So if we decide python1.5 is no longer supported, that's ok with me. Then the only serious problem is: > 3. Tried to run the demos, and it failed. From the tmp dir: > ... > > trinity$ python2 ./pythondemos.py > Traceback (most recent call last): > File "./pythondemos.py", line 15, in ? > from plplot import * > File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? > from plplotc import * > ImportError: dynamic module does not define init function (initplplotc) p.s. I did configure with --enable-dyndrivers. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Alan W. I. <ir...@be...> - 2002-08-19 16:58:04
|
Maurice, it is possible with enough hacking around you could get python2 to work properly for RedHat, but I don't trust it since I could not make it work in RH 7.2 even though I spent a lot of effort. Therefore, could you undo that symlink and try the default python (1.5) command with my setup.py.in change? Hopefully, that will solve all the 1.5 problems, but if not, I am willing to help until they are solved. Alan On Mon, 19 Aug 2002, Maurice LeBrun wrote: > Maurice LeBrun writes: > > [python1.5 vs python2.2 problems] > > BTW a symlink from /usr/bin/python2.2 to ~/bin/python took care of all of > these problems. Probably RedHat will go with python == python2.2 starting > with their 8.0 release, but for now the symlink solution works fine. So > if we decide python1.5 is no longer supported, that's ok with me. > > Then the only serious problem is: > > > 3. Tried to run the demos, and it failed. From the tmp dir: > > ... > > > > trinity$ python2 ./pythondemos.py > > Traceback (most recent call last): > > File "./pythondemos.py", line 15, in ? > > from plplot import * > > File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? > > from plplotc import * > > ImportError: dynamic module does not define init function (initplplotc) > > p.s. I did configure with --enable-dyndrivers. > > -- > Maurice LeBrun mj...@ga... > Research Organization for Information Science and Technology of Japan (RIST) > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Plplot-devel mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-devel > |
From: Alan W. I. <ir...@be...> - 2002-08-19 16:42:37
|
On Mon, 19 Aug 2002, Maurice LeBrun wrote: > Just a FYI. I decided to try once again to get the python bindings to work on > my RH7.3 machines. First I built & installed the latest swig, making sure it > came first in my path, and then that part was traversed correctly. Good! > However > more problems: > > 1. During the make I get: > > python setup.py build --force --build-temp="./" --build-lib="./" --flat > Traceback (innermost last): > File "setup.py", line 45, in ? > libs_list = libs.split(" ") > AttributeError: 'string' object has no attribute 'split' > make: *** [plplotcmodule.so] Error 1 > > where "python" for RH7.3 is python1.5. Is python1.5 no longer supported? We should support it for now, and thanks very much for testing that support (which I cannot do on my Debian system which is fully converted to python 2). Before, I found python2 was not reliable in RH7.2 so I used python1.5 in that case. If you look at plplot/rpm/plplot_redhat7.2.spec, you will see I did the following there: PY_VERSION=`python -c 'import sys ; print sys.version[0:3]'` export PYTHON_INC_DIR=/usr/include/python${PY_VERSION}/ echo PYTHON_INC_DIR=${PYTHON_INC_DIR} export PYTHON_MOD_DIR=/usr/lib/python${PY_VERSION}/ export PYTHON_CFG_DIR=${PYTHON_MOD_DIR}/config export PYTHON_NUM_DIR=${PYTHON_INC_DIR}/Numeric/ export PYTHON_MACH_DIR=${PYTHON_MOD_DIR}/site-packages export PYTHON_DIR=${PYTHON_MACH_DIR} ./configure ... I would stick with python-1.5 until RedHat are confident enough of python-2 to call the associated command "python" rather than "python2". To solve the above and other split problems, I have just committed a revised setup.py.in to cvs which replaces the python 2.x method, e.g., incs_list = incs.split(" ") with the python 1.5 (and python 2.x) string function incs_list = string.split(incs," ") Please give that a try, and I hope that weeds out all python-2 only constructs that have crept in since plplot-5.1.0. Alan |
From: Maurice L. <mj...@ga...> - 2002-08-20 11:10:16
|
Alan W. Irwin writes: > On Mon, 19 Aug 2002, Maurice LeBrun wrote: > > where "python" for RH7.3 is python1.5. Is python1.5 no longer supported? > > We should support it for now, and thanks very much for testing that support > (which I cannot do on my Debian system which is fully converted to python 2). > > Before, I found python2 was not reliable in RH7.2 so I used python1.5 in > that case. [...] OK, I fixed sysloc.in so that I could configure with: PYTHON_INC_DIR=/usr/include/python1.5 ./configure --enable-python and get the correct Numeric arrayobject.h file. But still no go: trinity$ python ./pythondemos.py Traceback (innermost last): File "./pythondemos.py", line 15, in ? from plplot import * File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? from plplotc import * ImportError: /home/mjl/dev/plplot/plpy/tmp/plplotcmodule.so: undefined symbol: PySequence_Fast_GET_ITEM Turns out plplotcmodule.i relies on some things present in 2.x but not in 1.5, such as this macro define and the PySequence_Size() call. The macro define could probably just be replicated here but dunno what to do about PySequence_Size(). Grep for these in python's abstract.h file for more info. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Alan W. I. <ir...@be...> - 2002-08-20 15:12:41
|
Thanks, Maurice, for investigating the python1.5 possibility further. Gary, do you think it would be straightforward to get plplotcmodule.i working for python-1.5 or do you think we should just forget about python-1.5 support and only support python-2? From your previous messages, I notice you have gotten plplot to work for RedHat. Was that for their python2 variant? Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ On Tue, 20 Aug 2002, Maurice LeBrun wrote: > Alan W. Irwin writes: > > On Mon, 19 Aug 2002, Maurice LeBrun wrote: > > > where "python" for RH7.3 is python1.5. Is python1.5 no longer supported? > > > > We should support it for now, and thanks very much for testing that support > > (which I cannot do on my Debian system which is fully converted to python 2). > > > > Before, I found python2 was not reliable in RH7.2 so I used python1.5 in > > that case. [...] > > OK, I fixed sysloc.in so that I could configure with: > > PYTHON_INC_DIR=/usr/include/python1.5 ./configure --enable-python > > and get the correct Numeric arrayobject.h file. But still no go: > > trinity$ python ./pythondemos.py > Traceback (innermost last): > File "./pythondemos.py", line 15, in ? > from plplot import * > File "/home/mjl/dev/plplot/plpy/tmp/plplot.py", line 20, in ? > from plplotc import * > ImportError: /home/mjl/dev/plplot/plpy/tmp/plplotcmodule.so: undefined symbol: > PySequence_Fast_GET_ITEM > > Turns out plplotcmodule.i relies on some things present in 2.x but not in 1.5, > such as this macro define and the PySequence_Size() call. The macro define > could probably just be replicated here but dunno what to do about > PySequence_Size(). Grep for these in python's abstract.h file for more info. > > -- > Maurice LeBrun mj...@ga... > Research Organization for Information Science and Technology of Japan (RIST) > |