matplotlib-users Mailing List for matplotlib

On 21.05.2007, at 19:55, Christopher Barker wrote:
> Please don't cross-post quite so much!
My apologies for make so much fuzz about this!
(But is a posting to two mailing lists really posted too wide?)
> there are some issues with building MPL against wxPython, but it looks
> like you've got wxPython problems anyway -- so you need to resolve =20
> those
> first. The macports or wxPython lists are your best bet for that.
There were actually problems with the MacPorts python-2.4 port, which =20=
re resolved by now. The details are given here:
 http://trac.macports.org/projects/macports/changeset/25391
> wxPython was built against a particular version of wxWidgets -- I
> suspect you've got more than one version of wxWidgets on there,
Well, no.
Maybe MacPorts updated wxPython before wxWidgets, but in principle =20
that should not (and normally does not) happen either.
> Or just go back and re-install wxPython, making sure you follow all =20=
> the
> steps correctly -- how did you did that in the first place?
MacPorts does it for me;)
> PS: this will probably be easier if you use the macpython version of
> python/wxpython/MPL -- do you need macports for a reason?
Yes, it gives me all the Unix tools I need from a single place and in =20=
a very clean way, including dependency tracking and clean uninstalls =20
or upgrades...
Anyway, thank you very much for your suggestions.
A big thank you to everybody who has contributed to matplotlib and =20
wxWidgets/wxPython for great products!
Greetings,
Jochen
--=20
Einigkeit und Recht und Freiheit http://www.Jochen-=20
Kuepper.de
 Libert=E9, =C9galit=E9, Fraternit=E9 GnuPG key: =
CC1B0B4D
 Sex, drugs and rock-n-roll

First:
Please don't cross-post quite so much!
Second:
there are some issues with building MPL against wxPython, but it looks 
like you've got wxPython problems anyway -- so you need to resolve those 
first. The macports or wxPython lists are your best bet for that.
> For wxPython: I get the same error when trying to import wxpython or wx 
> directly in a fresh python:
> UserWarning: wxPython/wxWidgets release number mismatch
> warnings.warn("wxPython/wxWidgets release number mismatch")
wxPython was built against a particular version of wxWidgets -- I 
suspect you've got more than one version of wxWidgets on there, and it's 
finding the wrong one. I don't use macports, so I'm not sure how it 
should be set up, but I'd look for files starting with "lib_wx", and see 
what versions you find.
Or just go back and re-install wxPython, making sure you follow all the 
steps correctly -- how did you did that in the first place?
-Chris
PS: this will probably be easier if you use the macpython version of 
python/wxpython/MPL -- do you need macports for a reason?
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

On Monday 21 May 2007 01:28:27 pm Johann Cohen-Tanugi wrote:
> I am closing the issue I had with ghostscript : I just built in
> /usr/local ghostscript 8.56 and now saving in eps file does not truncate
> the figure anymore.
Good news, thanks for the update.
> Thanks to Darren for pointing out that the FC5 version of ghostscript is
> way old.... And it looks like the FC7 version is as old !!
> Probably a licensing issue.
It's not a licensing issue; many linux distributions ship ESP ghostscript 
because it supposedly works better with the CUPS printing system. I have been 
using GPL ghostscript with CUPS for a long time, with no complaints. But here 
is some good news: ESP cups is merging with GPL cups as of version 8.57, and 
the ESP project will be discontinued.
> Darren Dale wrote:
> > On Monday 21 May 2007 10:42:26 am you wrote:
> >> hi Darren,
> >> thanks. I am not sure what you have in mind with the GPL.... My
> >> ghostscript rpm are :
> >> [cohen@localhost ~]$ rpm -qa | grep ghostscript
> >> ghostscript-devel-8.15.2-1.1
> >> ghostscript-8.15.2-1.1
> >> ghostscript-fonts-5.50-13.1
> >> ghostscript-gtk-8.15.2-1.1
> >
> > There are three different versions of ghostscript: AFPL, GPL (formerly
> > GNU), and ESP ghostscript. You most likely have ESP ghostscript.
> > Fortunately, I just read that ESP and GPL ghostscript are merging as of
> > version 8.57, and the ESP project will be discontinued.
> >
> >> Given the fact that I use FC5 I would be surprised to be using very old
> >> versions, which then would cause problems.
> >
> > GPL 8.15 was released almost 3 years ago.
> >
> >> I had more in mind
> >> configuration probl;ems or mismatch....
> >
> > There have been all kinds of problems reported on this mailing list with
> > usetex that were solved by upgrading ghostscript to 8.54.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
Darren S. Dale, Ph.D.
Staff Scientist
Cornell High Energy Synchrotron Source
Cornell University
275 Wilson Lab
Rt. 366 & Pine Tree Road
Ithaca, NY 14853
dd...@co...
office: (607) 255-3819
fax: (607) 255-9001
http://www.chess.cornell.edu

I am closing the issue I had with ghostscript : I just built in 
/usr/local ghostscript 8.56 and now saving in eps file does not truncate 
the figure anymore.
Thanks to Darren for pointing out that the FC5 version of ghostscript is 
way old.... And it looks like the FC7 version is as old !!
Probably a licensing issue.
Anyway, thanks.
Johann
Darren Dale wrote:
> On Monday 21 May 2007 10:42:26 am you wrote:
> 
>> hi Darren,
>> thanks. I am not sure what you have in mind with the GPL.... My
>> ghostscript rpm are :
>> [cohen@localhost ~]$ rpm -qa | grep ghostscript
>> ghostscript-devel-8.15.2-1.1
>> ghostscript-8.15.2-1.1
>> ghostscript-fonts-5.50-13.1
>> ghostscript-gtk-8.15.2-1.1
>> 
>
> There are three different versions of ghostscript: AFPL, GPL (formerly GNU), 
> and ESP ghostscript. You most likely have ESP ghostscript. Fortunately, I 
> just read that ESP and GPL ghostscript are merging as of version 8.57, and 
> the ESP project will be discontinued.
>
> 
>> Given the fact that I use FC5 I would be surprised to be using very old
>> versions, which then would cause problems. 
>> 
>
> GPL 8.15 was released almost 3 years ago.
>
> 
>> I had more in mind 
>> configuration probl;ems or mismatch....
>> 
>
> There have been all kinds of problems reported on this mailing list with 
> usetex that were solved by upgrading ghostscript to 8.54.
> 

Hi Johann,
Just make sure you are using the same version (GPL version 8.54?) as the 
others who are not having problems. That advice is about the best I can do. 
This mailing list is not for ghostscript support.
Darren 
On Monday 21 May 2007 1:14:36 am Johann Cohen-Tanugi wrote:
> hi there,
> out of idea I decided to download gsview and try to open my eps file
> with it. It still showed it truncated but this time gsview has resizing
> capabilities, and I could actually reformat the plot so that it shows
> the whole figure and then save it. Given the fact that Matthew could not
> reproduce my issue and noticed that the ps figure was looking slightly
> different, I have the feeling that somehow ghostscript is not behaving
> correctly on my system, though I have no clue why or how. Is anyone
> expert in these matters around?
>
> thanks a lot,
> Johann
>
> Matthew Auger wrote:
> > I was having the same problem, but the recent xpdf thread pointed me
> > to a/the solution. I was able to successfully run your script by
> > outputting as eps instead of ps (which produced truncated output, as
> > you were experiencing).
> >
> > Matt
> >
> > On 2007年5月10日, Johann Cohen-Tanugi wrote:
> >> Well, matplotlib starts with a canvas bigger than my screen
> >> (vertically only) but in the end it seems to resize it so everything
> >> fits in. I can see the whole drawing and the bottom toolbar. Again,
> >> saving in png or jpg works perfectly.... and of course I checked that
> >> gv was not cutting the graph when displaying it.
> >> I just tried to use GTK as a backend, and ipython tells me that there
> >> are "non implemented" errors on my script....
> >> I attach it here.
> >> thanks!
> >> Johann
> >>
> >> Darren Dale wrote:
> >>> On Wednesday 09 May 2007 12:19:24 pm Johann Cohen-Tanugi wrote:
> >>>> I am creating a "big" drawing ( figure(figsize=(16,20)) ), and when I
> >>>> try to save it in eps/ps form, it mishandle the overall size and only
> >>>> save a portion of the drawing. Saving in png or jpg works fine though.
> >>>> Any idea?
> >>>
> >>> On my system, you cant create a figure that is larger than the
> >>> monitor size, unless I use a non-gui backend like agg or ps. It
> >>> doesnt matter whether I save an eps, png, or jpg. Also, make sure
> >>> your postscript viewer is not truncating the page due to an
> >>> inappropriate page size setting.
> >>>
> >>> Darren
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
Darren S. Dale, Ph.D.
dd...@co...

hi there,
out of idea I decided to download gsview and try to open my eps file 
with it. It still showed it truncated but this time gsview has resizing 
capabilities, and I could actually reformat the plot so that it shows 
the whole figure and then save it. Given the fact that Matthew could not 
reproduce my issue and noticed that the ps figure was looking slightly 
different, I have the feeling that somehow ghostscript is not behaving 
correctly on my system, though I have no clue why or how. Is anyone 
expert in these matters around?
thanks a lot,
Johann
Matthew Auger wrote:
> I was having the same problem, but the recent xpdf thread pointed me 
> to a/the solution. I was able to successfully run your script by 
> outputting as eps instead of ps (which produced truncated output, as 
> you were experiencing).
>
> Matt
>
>
> On 2007年5月10日, Johann Cohen-Tanugi wrote:
>
>> Well, matplotlib starts with a canvas bigger than my screen 
>> (vertically only) but in the end it seems to resize it so everything 
>> fits in. I can see the whole drawing and the bottom toolbar. Again, 
>> saving in png or jpg works perfectly.... and of course I checked that 
>> gv was not cutting the graph when displaying it.
>> I just tried to use GTK as a backend, and ipython tells me that there 
>> are "non implemented" errors on my script....
>> I attach it here.
>> thanks!
>> Johann
>>
>> Darren Dale wrote:
>>> On Wednesday 09 May 2007 12:19:24 pm Johann Cohen-Tanugi wrote:
>>>
>>>> I am creating a "big" drawing ( figure(figsize=(16,20)) ), and when I
>>>> try to save it in eps/ps form, it mishandle the overall size and only
>>>> save a portion of the drawing. Saving in png or jpg works fine though.
>>>> Any idea?
>>>>
>>>
>>> On my system, you cant create a figure that is larger than the 
>>> monitor size, unless I use a non-gui backend like agg or ps. It 
>>> doesnt matter whether I save an eps, png, or jpg. Also, make sure 
>>> your postscript viewer is not truncating the page due to an 
>>> inappropriate page size setting.
>>>
>>> Darren
>>>