Matplotlib and wxPython

wxPython Users
1

Hi all,

I just compiled Matplotlib 0.85 with the WXAgg back end.

It seems to work fine, but when I run it, I get:

** (python2.4:24617): WARNING **: failed request with status 200

(python2.4:24617): GnomePrintCupsPlugin-WARNING **: iconv does not support ppd character encoding: ISOLatin1, trying CSISOLatin1

** (python2.4:24617): WARNING **: failed request with status 200

This happens with pylab.show(), or if I use wxmpl.PlotPanel in an App of my own.

I haven't noticed this in any other wxPython apps. I have no idea how to debug this, as it's not an error at the Python level.

Linux Fedora Core4
Python 2.4.1
wxPython '2.6.1.0' (gtk2-unicode[
matplotlib 0.85

Anyone have any ideas?

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer
                                         
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

2

Christopher Barker wrote:

Hi all,

I just compiled Matplotlib 0.85 with the WXAgg back end.

It seems to work fine, but when I run it, I get:

** (python2.4:24617): WARNING **: failed request with status 200

(python2.4:24617): GnomePrintCupsPlugin-WARNING **: iconv does not support ppd character encoding: ISOLatin1, trying CSISOLatin1

** (python2.4:24617): WARNING **: failed request with status 200

This happens with pylab.show(), or if I use wxmpl.PlotPanel in an App of my own.

I haven't noticed this in any other wxPython apps.

Try running the PrintFramework demo. I get the same warning messages there, but they don't seem to indicate any real problems (the printout still happens.)

I have no idea how to debug this, as it's not an error at the Python level.

I'm not sure exactly where they are coming from either, but my guess is that it is the gnomeprint library.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

3

Robin Dunn wrote:

Try running the PrintFramework demo. I get the same warning messages there, but they don't seem to indicate any real problems (the printout still happens.)

Yup, same error there. I haven't seen any real problems either, but it's annoying to get these kinds of messages.

I'm not sure exactly where they are coming from either, but my guess is that it is the gnomeprint library.

I agree. and now we've really gotten out of my depth. I wonder if anyone on wx-dev would have a clue?

oh well, we've all got more important things to do....

thanks,

- Chris

···

--
Christopher Barker, Ph.D.
Oceanographer
                                         
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

4

I just compiled Matplotlib 0.85 with the WXAgg back end.

It seems to work fine, but when I run it, I get:

<errors snipped>

This happens with pylab.show(), or if I use wxmpl.PlotPanel in an App of my own.

This looks like another weird wxPython/wxWidgets/Gnome/CUPS problem, similar to the one Ryan Krauss had in October. Given that you're getting very different error messages, I'm not sure that his solution is applicable:

So, it appears this is a problem with CUPS and wxPython. I had never
plugged a printer into this fairly new installation of ubuntu. After
doing so and making sure that cups is running, the IPP error went
away.

Based on the strace output, I believe that the warning is getting generated
when trying to start up CUPS (`/etc/cups/client.conf' is opened at line
10484), from within lincups, which is loaded by libgnomeprintcups, which is
loaded by libgnomeprint, which is loaded by wxWidgets, which is loaded by
wxPython (whee!). Do you have a working CUPS installation on your computer?
If that's not the solution, then I don't know what is; try emailing the
wxPython-users list.

I haven't noticed this in any other wxPython apps. I have no idea how to debug this, as it's not an error at the Python level.

I had Ryan send me some strace output:
  $ strace python -c short_wxagg_script.py > strace.txt 2>&1

You probably don't want to send it to the lists, but I'll be happy to take a look at it. I also have the strace output from October, if that would help the wxPython gurus better understand what's going on.

Another useful bit of information would be whether or not the wxPython demo's printing framework example causes the same errors when you run it. That might help us nail down the source of the problem (e.g. is it at the wxPython-level, or something WxAgg is doing to wxPython, or the inclusion of the printing framework?).

Ken

···

On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:
On Oct 20, 2005, at 5:12 PM, Ryan Krauss wrote:

On 10/20/05, Ken McIvor <mcivor@iit.edu> wrote:

On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:

5

I actually also get the ISOLatin1 warning (after I got rid of my other
problem that Ken mentioned). I put a little effort into tracking it
down, but not much and didn't find a solution.

Ryan

···

On 12/29/05, Ken McIvor <mcivor@iit.edu> wrote:

On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:
> I just compiled Matplotlib 0.85 with the WXAgg back end.
>
> It seems to work fine, but when I run it, I get:
<errors snipped>
> This happens with pylab.show(), or if I use wxmpl.PlotPanel in an
> App of my own.

This looks like another weird wxPython/wxWidgets/Gnome/CUPS problem,
similar to the one Ryan Krauss had in October. Given that you're
getting very different error messages, I'm not sure that his solution
is applicable:

On Oct 20, 2005, at 5:12 PM, Ryan Krauss wrote:
> So, it appears this is a problem with CUPS and wxPython. I had never
> plugged a printer into this fairly new installation of ubuntu. After
> doing so and making sure that cups is running, the IPP error went
> away.
>
> On 10/20/05, Ken McIvor <mcivor@iit.edu> wrote:
>> Based on the strace output, I believe that the warning is getting
>> generated
>> when trying to start up CUPS (`/etc/cups/client.conf' is opened at
>> line
>> 10484), from within lincups, which is loaded by libgnomeprintcups,
>> which is
>> loaded by libgnomeprint, which is loaded by wxWidgets, which is
>> loaded by
>> wxPython (whee!). Do you have a working CUPS installation on your
>> computer?
>> If that's not the solution, then I don't know what is; try
>> emailing the
>> wxPython-users list.

On Dec 28, 2005, at 6:29 PM, Christopher Barker wrote:
> I haven't noticed this in any other wxPython apps. I have no idea
> how to debug this, as it's not an error at the Python level.

I had Ryan send me some strace output:
        $ strace python -c short_wxagg_script.py > strace.txt 2>&1

You probably don't want to send it to the lists, but I'll be happy to
take a look at it. I also have the strace output from October, if
that would help the wxPython gurus better understand what's going on.

Another useful bit of information would be whether or not the
wxPython demo's printing framework example causes the same errors
when you run it. That might help us nail down the source of the
problem (e.g. is it at the wxPython-level, or something WxAgg is
doing to wxPython, or the inclusion of the printing framework?).

Ken

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org