gnuplot-py-users Mailing List for Gnuplot.py

Dear Gnuplot-py-users,

I found this problem was a know issue and discussed at support page
(http://sourceforge.net/tracker/index.php?func=detail&aid=416091&group_id=17434&atid=217434).

Gnuplot.py works on win32 by following instruction in this support page.

Hiroshi

Hiroshi Watabe
wa...@ri...

Dear Hiroshi,

>   File "c:\python22\Lib\site-packages\Gnuplot\_Gnuplot.py", line 206, in __call__
>     self.gnuplot(s)
>   File "c:\python22\lib\site-packages\Gnuplot\gp_win32.py", line 124, in __call__
>     self.write(s + '\n')
> IOError: [Errno 22] Invalid argument
> 
> It seems to me that python cannot properly pass argument to
> 'pgnuplot.exe'.

It looks to me that it doesn't even find gnuplot.exe
Is this executable in the executable path ?. It must be. 
Otherwise you can specify the full path to the gnuplot_command
in your system (but you will need to do that for each
release)

I do not run windows, but I changed the gnuplot_command to a 
non existent name in my Linux box and I get an error message
somehow similar to yours. 

Best luck,
-- Leo

Hi Michael !

Thank you for the changes, I tried the CVS version and it works
perfectly in my Linux box (I reverted my dirty fix in my overloaded
gnuplot class). I tried plotting very large (thus slow) surface plots with
no problems. I rerun my codes with no problmes. It seems rock solid.
Great work !

> 1. The PlotItem interface is changed a little bit (the constructor

Ok with me, I personally don't use it directly :-)

> 2. The hierarchy of classes derived from PlotItem is changed
>    significantly.  

Same as above.

> The changes to the majority of the user interface are really quite
> minor; I think only power-users will notice any difference at all.

Yes. Still, you may want to consider naming the next release 2.0,
to make clear that there are structural changes. Also, it
may be a good idea to release a release candidate first and 
let people try it for a while (up to you of course) and give
feedback. This list is fairly new and it has a few users ...

> It would be great if Unix users would grab the new version and test it
> out a little bit, especially within your own applications.  This
> request is especially directed at those users who have been
> "agitating" for such a change!

Say what ???. :-)

Thank you so much Michael

Best,
-- Leo

Hi,

Due to popular demand, I just hacked together some changes to
Gnuplot.py to allow data to be sent to gnuplot via FIFOs (named pipes)
under Unix.  This seems to be a reliable solution for knowing when to
delete temporary files.  For example, test.py runs perfectly even if I
take out all of the delays!  I have checked the changes into CVS.

This new FIFO feature is only implemented under Unix because Python
doesn't support FIFOs under other operating systems.  Other OSs
continue to use temporary files and/or inline data.

However, in the process of rewriting, I had to change the internals of
the PlotItems class hierarchy.  Before I incorporate the changes into
a release I would like to check whether they're going to cause
backwards-compatibility problems with users.  So you, the elite
members of the gnuplot-py-users mailing list, get to exert some
influence!  Let me know if any of the following things would upset
you:

1. The PlotItem interface is changed a little bit (the constructor
   arguments change and a couple new member functions have been
   added).  Has anybody derived new classes from PlotItem?  If so,
   your classes would have to be changed a little bit.

2. The hierarchy of classes derived from PlotItem is changed
   significantly.  For example, File and Data have been changed from
   actual classes into helper functions that return instances of a new
   _FileItem class.  This might be a problem for anybody who works
   with the internals of PlotItems, for example, to derive entirely
   new PlotItem classes.

3. The AnyFile and TempFile classes were removed as they are no longer
   useful within the Gnuplot.py implementation.  Does anybody use
   those classes externally and would be sad to see them go?

The changes to the majority of the user interface are really quite
minor; I think only power-users will notice any difference at all.
For example, everything in test.py ran perfectly after changing
essentially only the example that created a TempFile explicitly.

It would be great if Unix users would grab the new version and test it
out a little bit, especially within your own applications.  This
request is especially directed at those users who have been
"agitating" for such a change!

Yours,
Michael

--
Michael Haggerty
mh...@al...

Dear Gnuplot-py users,

I tried to run Gnuplot-py on Win32 but I got following error messages;

python demo.py
Traceback (most recent call last):
  File "demo.py", line 121, in ?
    demo()
  File "demo.py", line 72, in demo
    g.ylabel('x^2') # take advantage of enhanced postscript mode
  File "c:\python22\Lib\site-packages\Gnuplot\_Gnuplot.py", line 434, in ylabel
    self.set_string('ylabel', s)
  File "c:\python22\Lib\site-packages\Gnuplot\_Gnuplot.py", line 381, in set_string
    self('set %s "%s"' % (option, s))
  File "c:\python22\Lib\site-packages\Gnuplot\_Gnuplot.py", line 206, in __call__
    self.gnuplot(s)
  File "c:\python22\lib\site-packages\Gnuplot\gp_win32.py", line 124, in __call__
    self.write(s + '\n')
IOError: [Errno 22] Invalid argument

It seems to me that python cannot properly pass argument to
'pgnuplot.exe'.

I use
 gnuplot-py-1.6
 python-2.2
 gnuplot-3.71

How can I solve this problem? 

Thank you in advance.

Hiroshi

Hiroshi Watabe
wa...@ri...