[Plplot-devel] python status under RH7.3 (was decoupling drivers from libplplot)

[Alan W. I. <ir...@be...>]

In answer to Geoffrey's implied question about RH7.3 python status:

Different Numeric rpm's are required depending on whether you are using
python1.5 or python2.1 or 2.2.  In the first case, use
http://prdownloads.sf.net/numpy/python-numpy-15.3-1.i386.rpm.  In the latter
case for Debian with python2.1, I use the Debian package that goes with
python2.1 which is Numeric version 21.0.  Because the Numeric version
numbers seem to be the python version multiplied by 10, then do the
appropriate multiplication to find the correct rpm for you in
http://prdownloads.sf.net/numpy/.  There are several 21.0 and 22.0 rpm's
there.

That should bring you up to speed to where Maurice was. I am reposting what
I said below (which summarizes the RH 7.3 python status) to the list in
answer to his last python question.  I don't believe Maurice followed up on my
suggested solution so I don't know whether dropping "module" from the shared
object name will work or not, but I am guessing it will.

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
__________________________

---------- Forwarded message ----------
Date: Fri, 23 Aug 2002 09:51:03 -0700 (PDT)
From: Alan W. Irwin <ir...@uv...>
Cc: PLplot development list <Plp...@li...>
Subject: Re: [Plplot-devel] problems with python bindings under RH7.3

On Thu, 22 Aug 2002, Maurice LeBrun wrote:

> Good news and bad news.  The bad news is, it still doesn't work.  The good
> news is that it's the exact same error message I got with python2.2, so maybe
> if a solution is found it will apply to both.  Here it is:
>
> 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: dynamic module does not define init function (initplplotc)


That reminds me of an error that Olof was getting on windows.  The solution
was to drop "module" from the name of the created shared object (i.e
plplotc.so rather than plplotcmodule.so).  I wondered at the time whether
the windows version of python was no longer supporting those legacy-style
'module.so names, but perhaps it is Debian that is the odd man out by still
allowing them.  Note Gary has always used *.so names with "module"
dropped, and that may be one key to his success on RedHat (and windows and
mac os x).

To try the shortened names, in plplot/tmp remove plplotcmodule.so and
plplot_widgetmodule.so and change the lines in the (configure-generated)
setup.py from

module1 = Extension( "plplotcmodule",  ==>
module1 = Extension( "plplotc",

and

module2 = Extension( "plplot_widgetmodule",  ==>
module2 = Extension( "plplot_widget",

Then execute make to generate plplotc.so and plplot_widget.so, etc. Let us
know if that works.  If it does, then go ahead and make the permanent
setup.py.in changes and the modest configuration changes to do with the
changed plplot*.so names.

If that doesn't work for you, then my plan is to copy my test environment to
a RH 7.3 box I have access to and then figure out what is best to do for
that environment. However, I have no time to pursue that now.  It would be at
the top of my PLplot agenda once I have a chance to work on PLplot again in
September or October, but I am hoping somebody else will figure it out before
then.

Alan



-------------------------------------------------------
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