Re: [Plplot-devel] python README (Was: Wish list for the release--various thoughts.)

[Joao C. <jc...@fe...>]

On Friday 18 January 2002 5:13 am, Geoffrey Furnish wrote:
> Jo=E3o Cardoso writes:
>  > Again CVS logs don't lie: the files in that subdir (Setup and
>  > _tkinter.c) are a "Complete sample of files edited according to the
>  > prescription in bindings/python/README". They must be leftovers from
>  > the static python building, I guess.
>  >
>  > My concern with unknow source or configuration files in cvs is...
>  > concern. New people may lose time looking what they are for, there
>  > might be configuartion support for them, turning configuration issue=
s
>  > more complicated, there might be side-effects, etc.
>
> Mmm, well, I wouldn't call them "leftovers", in thee sense of having
> become obsolete or something.  I personally don't use the PLplot
> python binding any other way than by using the static binding, because
> that gives me access to the plframe widget, which is not yet available
> any other way.  So I do not want to see stuff pertaining to the static
> plplot python binding removed, until we recover plframe via TEA inside
> python/Tk.  I figure that's still a ways out.

OK, I understand it now.

Are the following statements in bindings/python/README still true?

"How to build yourself a python with PLplot support
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

There are two possibilities.  You can try to build a dynamically
loadable python module, or you can modify the python build to include
the plplot module.  The former is what configure will try to do if you
use --enable-python (which is the default).  Currently this does not
work very well.  I have had some success with this plan on Linux, but
not on other Unices yet.  So, I suggest, and this document describes,
to modify the python and rebuild it."=09

Joao