matplotlib-users Mailing List for matplotlib (Page 2)

Darren Dale wrote:
> The cache string included the latex font package, but this is not necessarily 
> enough. pslatex, for example, will load the adobe fonts, but the output still 
> depends on whether font.family is set to serif (times) or sans-serif 
> (helvetica). I just added the font.family info to the cache string, that 
> seems to take care of it.
If I can make a suggestion: in
http://new.scipy.org/Wiki/Cookbook/Matplotlib/UsingTex
it might be worth clarifying exactly how font.family interacts with the 
various latex package options. I think in particular the combination of 
serif/sans vs. the font.latex.package choice (helvet/typec1m/...) is a little 
bit confusing.
Cheers,
f

>>>>> "Darren" == Darren Dale <dd...@co...> writes:
 Darren> s+='latex font: %s %s'%
 Darren> (rcParams['font.latex.package'], rcParams['font.family'])
 Darren> So it should not be necessary to clear your tex.cache.
Oops, I also added the font.family to the Agg key
Checking in lib/matplotlib/backends/backend_agg.py;
/cvsroot/matplotlib/matplotlib/lib/matplotlib/backends/backend_agg.py,v
<-- backend_agg.py
new revision: 1.42; previous revision: 1.41
It would be useful to centralize the cache key generation, since it is
fragile to have texmanager and backend_agg doing this
independently....
JDH

On Sunday 29 January 2006 11:57 am, you wrote:
> >>>>> "Ryan" == Ryan Krauss <rya...@gm...> writes:
>
> Ryan> That seems to have done it. And CVS is caught up for
> Ryan> non-developers. Thanks for all your hard work Darren. I
> Ryan> can now have my choice of serif or san-serif fonts and the
> Ryan> eps files match the screen. You can still have problems if
> Ryan> you change your rc file without clearing you tex.cache. I
> Ryan> don't know if a note about that in the rc file would cut
> Ryan> down on problems or not.
>
> What are you changing that is causing the problem? I have tried to
> include the font family information in the cache string. Please give
> us an exact sequence of steps that is causing the problem, starting
> with a clean CVS build an empty cache.
The cache string included the latex font package, but this is not necessarily 
enough. pslatex, for example, will load the adobe fonts, but the output still 
depends on whether font.family is set to serif (times) or sans-serif 
(helvetica). I just added the font.family info to the cache string, that 
seems to take care of it.
Darren

On Sunday 29 January 2006 11:53 am, you wrote:
> That seems to have done it. And CVS is caught up for non-developers.
> Thanks for all your hard work Darren. 
My pleasure.
> I can now have my choice of 
> serif or san-serif fonts and the eps files match the screen. You can
> still have problems if you change your rc file without clearing you
> tex.cache. I don't know if a note about that in the rc file would cut
> down on problems or not.
Thanks for pointing this out. It is fixed in CVS, Line 79 in texmanager has 
been changed to read: 
 s+='latex font: %s %s'% (rcParams['font.latex.package'], 
 rcParams['font.family'])
So it should not be necessary to clear your tex.cache.

>>>>> "Andrea" == Andrea Gavana <and...@ti...> writes:
 Andrea> Hello Paul, thank you very much for your suggestion. I
 Andrea> played a little bit with the two_scaled.py demo, and it
 Andrea> works nicely for 2 different Y-axes. I have tried
 Andrea> different things in order to have 3 or 4 axes, but it
 Andrea> seems to me that it is impossible without having 2 axes
 Andrea> overlapped. Maybe I am missing something...
You are absolutely right that it would be nice to have independent
support for multiple axis lines. It is on the goals page. Chaco does
this well, but it will require some worrk to support this properly in
matplotlib.
JDH

>>>>> "Jochen" == Jochen Voss <vo...@se...> writes:
 Jochen> Hello, I use matplotlib to non-interactively convert a
 Jochen> pile of numbers into a diagram for may web page. My
 Jochen> problem: the resulting grid lines are not perfectly
 Jochen> straight, they seem to be undecided which of two pixel
 Jochen> rows they belong to. The lines (magnified and in ASCII
 Jochen> art) look a bit like
 Jochen> ******** ******** ****
 Jochen> ******** ******** ****** ****
 Jochen> How can I get straight and homogeneous lines?
Yes, that is annoying. I just made some changes to CVS to fix it. The
root of the problem is that Agg does subpixel rendering. I have some
hacks now to make it work right for grid lines, but a cleaner approach
would be to expose "use subpixel" to the GC, and allow the grid lines
to turn it off. 
Checking in src/_backend_agg.cpp;
/cvsroot/matplotlib/matplotlib/src/_backend_agg.cpp,v <--
_backend_agg.cpp
new revision: 1.98; previous revision: 1.97
JDH

>>>>> "Ryan" == Ryan Krauss <rya...@gm...> writes:
 Ryan> That seems to have done it. And CVS is caught up for
 Ryan> non-developers. Thanks for all your hard work Darren. I
 Ryan> can now have my choice of serif or san-serif fonts and the
 Ryan> eps files match the screen. You can still have problems if
 Ryan> you change your rc file without clearing you tex.cache. I
 Ryan> don't know if a note about that in the rc file would cut
 Ryan> down on problems or not.
What are you changing that is causing the problem? I have tried to
include the font family information in the cache string. Please give
us an exact sequence of steps that is causing the problem, starting
with a clean CVS build an empty cache.
Thanks,
JDH

I know Fernando had posted questions about changing the font package
and John said something about adding the font family to the cache
somehow. I was talking specifically of having problems when switching
from serif to sans-serif and needing to clear the cache when you do.
On 1/29/06, Ryan Krauss <rya...@gm...> wrote:
> That seems to have done it. And CVS is caught up for non-developers.
> Thanks for all your hard work Darren. I can now have my choice of
> serif or san-serif fonts and the eps files match the screen. You can
> still have problems if you change your rc file without clearing you
> tex.cache. I don't know if a note about that in the rc file would cut
> down on problems or not.
>
> Thanks again,
>
> Ryan
>
> On 1/29/06, Darren Dale <dd...@co...> wrote:
> > On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> > > I don't know what I am doing wrong, but I just checked out everything
> > > from cvs and when I go into the directory and do a sudo python
> > > setup.py install and then import matplotlib, it says my version is
> > > 0.86.2 and I still have the same problems as before. It seems like
> > > cvs versions always had a cvs at the end of them before.
> >
> > My version also says 0.86.2. Maybe the problem is that non-developer ch=
eckout
> > is lagging. Try checking out again, your backend_ps is the only file th=
at
> > required changing. If it still does not reflect the changes, just inser=
ted
> > the following lines into the RendererPS.draw_tex method at line 641:
> >
> > if rcParams['text.tex.engine'] =3D=3D 'latex':
> > fontcmd =3D {'sans-serif' : r'{\sffamily %s}',
> > 'monospace' : r'{\ttfamily %s}'}.get(
> > rcParams['font.family'], r'{\rmfamily %s}')
> > s =3D fontcmd % s
> >
> > These commands produced the attached eps file (fontfamily is sans-serif=
 in
> > matplotlibrc):
> >
> > In [1]: plot([2,3,4,5])
> > Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]
> >
> > In [2]: plot([1,2,3,4])
> > Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]
> >
> > In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capi=
tal i's
> > Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>
> >
> > In [4]: savefig('sans-serif.eps')
> >
> >
> >
> >
> >
>

That seems to have done it. And CVS is caught up for non-developers.=20
Thanks for all your hard work Darren. I can now have my choice of
serif or san-serif fonts and the eps files match the screen. You can
still have problems if you change your rc file without clearing you
tex.cache. I don't know if a note about that in the rc file would cut
down on problems or not.
Thanks again,
Ryan
On 1/29/06, Darren Dale <dd...@co...> wrote:
> On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> > I don't know what I am doing wrong, but I just checked out everything
> > from cvs and when I go into the directory and do a sudo python
> > setup.py install and then import matplotlib, it says my version is
> > 0.86.2 and I still have the same problems as before. It seems like
> > cvs versions always had a cvs at the end of them before.
>
> My version also says 0.86.2. Maybe the problem is that non-developer chec=
kout
> is lagging. Try checking out again, your backend_ps is the only file that
> required changing. If it still does not reflect the changes, just inserte=
d
> the following lines into the RendererPS.draw_tex method at line 641:
>
> if rcParams['text.tex.engine'] =3D=3D 'latex':
> fontcmd =3D {'sans-serif' : r'{\sffamily %s}',
> 'monospace' : r'{\ttfamily %s}'}.get(
> rcParams['font.family'], r'{\rmfamily %s}')
> s =3D fontcmd % s
>
> These commands produced the attached eps file (fontfamily is sans-serif i=
n
> matplotlibrc):
>
> In [1]: plot([2,3,4,5])
> Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]
>
> In [2]: plot([1,2,3,4])
> Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]
>
> In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capita=
l i's
> Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>
>
> In [4]: savefig('sans-serif.eps')
>
>
>
>
>

On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> I don't know what I am doing wrong, but I just checked out everything
> from cvs and when I go into the directory and do a sudo python
> setup.py install and then import matplotlib, it says my version is
> 0.86.2 and I still have the same problems as before. It seems like
> cvs versions always had a cvs at the end of them before.
My version also says 0.86.2. Maybe the problem is that non-developer checkout 
is lagging. Try checking out again, your backend_ps is the only file that 
required changing. If it still does not reflect the changes, just inserted 
the following lines into the RendererPS.draw_tex method at line 641:
 if rcParams['text.tex.engine'] == 'latex':
 fontcmd = {'sans-serif' : r'{\sffamily %s}',
 'monospace' : r'{\ttfamily %s}'}.get(
 rcParams['font.family'], r'{\rmfamily %s}')
 s = fontcmd % s
These commands produced the attached eps file (fontfamily is sans-serif in 
matplotlibrc):
In [1]: plot([2,3,4,5])
Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]
In [2]: plot([1,2,3,4])
Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]
In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capital i's
Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>
In [4]: savefig('sans-serif.eps')

Darren Dale wrote:
> On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
>> clearing the tex.cache doesn't seem to make a difference. times is
>> still the only package thae doesn't overflow the legend box and the on
>> screen is always san serif and the eps is always serif.
> 
> I think this is now fixed in cvs.
I made similar observations here. With matplotlib from cvs, an empty tex-cache,
without own matplotlibrc and setting
rcParams['text.usetex'] = True
I get sans-serif fonts on screen (I guess it is the WXAgg backend) and serif
fonts in the eps output and the legend box is mostly too small.
Regards, Christian

I don't know what I am doing wrong, but I just checked out everything
from cvs and when I go into the directory and do a sudo python
setup.py install and then import matplotlib, it says my version is
0.86.2 and I still have the same problems as before. It seems like
cvs versions always had a cvs at the end of them before.
On 1/28/06, Darren Dale <dd...@co...> wrote:
> On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
> > clearing the tex.cache doesn't seem to make a difference. times is
> > still the only package thae doesn't overflow the legend box and the on
> > screen is always san serif and the eps is always serif.
>
> I think this is now fixed in cvs.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
> clearing the tex.cache doesn't seem to make a difference. times is
> still the only package thae doesn't overflow the legend box and the on
> screen is always san serif and the eps is always serif.
I think this is now fixed in cvs.

clearing the tex.cache doesn't seem to make a difference. times is
still the only package thae doesn't overflow the legend box and the on
screen is always san serif and the eps is always serif.
On 1/28/06, Darren Dale <dd...@co...> wrote:
> On Saturday 28 January 2006 20:15, Ryan Krauss wrote:
> > Playing with this a little bit more, times and pslatex seem to be the
> > only settings for font.latex.package that make any difference. I
> > still don't get the pretty san serif font I get on the screen, but at
> > least the legend boxes are right. Does it make sense that the on
> > screen font is different? I thought that was coming from dvipng and
> > would be generated by latex. What is the on screen font and how do I
> > get it into my eps files?
>
> Shot in the dark: Try clearing you tex.cache.
>
> If you set pslatex, the adobe postscript fonts will be used instead of th=
e
> computer modern fonts. So if you do {\sffamily Print this in sans-serif} =
with
> pslatex, you get helvetica fonts. You can do the same with computer moder=
n.
>
> Times is a subset of pslatex, the computer modern fonts end up being used=
 for
> math.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Saturday 28 January 2006 20:15, Ryan Krauss wrote:
> Playing with this a little bit more, times and pslatex seem to be the
> only settings for font.latex.package that make any difference. I
> still don't get the pretty san serif font I get on the screen, but at
> least the legend boxes are right. Does it make sense that the on
> screen font is different? I thought that was coming from dvipng and
> would be generated by latex. What is the on screen font and how do I
> get it into my eps files?
Shot in the dark: Try clearing you tex.cache.
If you set pslatex, the adobe postscript fonts will be used instead of the 
computer modern fonts. So if you do {\sffamily Print this in sans-serif} with 
pslatex, you get helvetica fonts. You can do the same with computer modern.
Times is a subset of pslatex, the computer modern fonts end up being used for 
math.

Playing with this a little bit more, times and pslatex seem to be the
only settings for font.latex.package that make any difference. I
still don't get the pretty san serif font I get on the screen, but at
least the legend boxes are right. Does it make sense that the on
screen font is different? I thought that was coming from dvipng and
would be generated by latex. What is the on screen font and how do I
get it into my eps files?
Thanks,
Ryan
On 1/28/06, Ryan Krauss <rya...@gm...> wrote:
> I am having a problem with the fonts with the usetex option. My plots
> look beautiful on the screen and the labels are in a san-serif font
> that I would guess is Helvetica. My rc files has this setting in it:
> font.latex.package : type1cm
>
> But when I save these plots and include them in a LaTeX file (or look
> at them with a posscript viewer), the font seems to have switched to
> times and the legends don't fit in the legend boxes any more.
>
> What am I doing wrong?
>
> Ryan
>

I am having a problem with the fonts with the usetex option. My plots
look beautiful on the screen and the labels are in a san-serif font
that I would guess is Helvetica. My rc files has this setting in it:
font.latex.package : type1cm
But when I save these plots and include them in a LaTeX file (or look
at them with a posscript viewer), the font seems to have switched to
times and the legends don't fit in the legend boxes any more.
What am I doing wrong?
Ryan

> Here's the "offending" bit of wiki text from
http://new.scipy.org/Wiki/Cookbook/Matplotlib :
> 
> = Runtime error with recent numarray (1.5.0) =
> 
> I'm not sure where this goes, but matplotlib-0.86.2 contains the line
> 
> 
> if mask is not ma.nomask:
> 
> in lines.py (line 276). Recent versions of numarray do not have
nomask, the correct line should be:
> 
> if mask is not None:
> 
> Update: it seems this is only going to fail if you have numpy set as
your default numeric library, because the code in
matplotlib/numerix/ma/__init__.py defines nomask EXCEPT when you also
have numpy installed. Does matplotlib work with numpy now? I had gotten
that nomask error and thought I needed numarray.
Andrew,
The most recent matplotlib should work with all three. Travis made the 
changes you noted. First the change to ma.nomask was made to make mpl 
work with numpy, which has nomask, then the changes to ma/__init__.py so 
that it would continue working with Numeric and numarray. I have also 
tested it with all three.
Keeping bug discussions out of the cookbook is a good idea!
Eric

As many of you know, a number of us have been busy migrating the
scipy.org website to a new, more user-friendly wiki system. The new wiki
is up-and-running, is more-up-to-date, and prettier-to-look at than the
old site.
We are working to make scipy.org a portal website for all scientific
software written in Python, and not just for the packages numpy and
scipy, which happen to have their natural homes there. This wiki
structure allows peer-review-by-wiki, so please do not feel bashful
about updating any aspect of the wiki to suit your opinions.
The current address of the new site is http://new.scipy.org/Wiki Once we
go "live", we'll point http://scipy.org to this wiki.
Before we make the switch, however, there are a few things that need to
be done and a few things that should be done. This is a request for two
things:
1) Review the page http://new.scipy.org/Wiki/MigratingFromPlone and make
sure you can live with what it says. If you can't edit it.
2) Please undertake any of the tasks listed at that page. Update the
page that you're working on the task, and again when you're done.
3) (Optional) Bask in the glory of our shiny new website which will
allow NumPy/ SciPy/ Matplotlib/ IPython/ whateverelse to rule the
scientific computing world!
I'd like to ask that we try and complete these tasks as quickly as
possible. I know I'm asking a busy group of people to pitch in, but I
hope you'll agree the results will be worth it.
Thank you,
Andrew Straw
PS Sorry for the cross postings. I thought it would be important to get
as many hands involved as possible.

While reviewing the new scipy website ( http://new.scipy.org/Wiki ) to see when we can turn it "live", I've come across the following matplotlib discussion in the matplotlib cookbook.
I'd like 2 ask things:
1) can we fix the issues described? (are they already fixed?)
2) can we keep bug discussions off the cookbook?
Sorry to be such a cookbook-is-a-cookbook-not-a-bug-discussion-venue enforcer, but I think it's important we keep the cookbook as newbie-friendly as possible. I think discussions of bugs at the very top of the cookbook are going to scare newbies away.
Here's the "offending" bit of wiki text from http://new.scipy.org/Wiki/Cookbook/Matplotlib :
= Runtime error with recent numarray (1.5.0) =
I'm not sure where this goes, but matplotlib-0.86.2 contains the line
 if mask is not ma.nomask:
in lines.py (line 276). Recent versions of numarray do not have nomask, the correct line should be:
 if mask is not None:
Update: it seems this is only going to fail if you have numpy set as your default numeric library, because the code in matplotlib/numerix/ma/__init__.py defines nomask EXCEPT when you also have numpy installed. Does matplotlib work with numpy now? I had gotten that nomask error and thought I needed numarray.

Hello,
I use matplotlib to non-interactively convert a pile of numbers into a
diagram for may web page. My problem: the resulting grid lines are
not perfectly straight, they seem to be undecided which of two pixel
rows they belong to. The lines (magnified and in ASCII art) look
a bit like
 ******** ******** ****
 ******** ******** ****** ****
How can I get straight and homogeneous lines?
The gory details:
(1) This is a self-compiled version of matplotlib-0.86.2 on a Debian
 Sarge system. I used the following options in setup.py.
 rc =3D dict({'backend':'Agg', 'numerix':'numarray'})
 BUILD_IMAGE =3D 1
 BUILD_AGG =3D 1
 BUILD_GTKAGG =3D 0
 BUILD_GTK =3D 0
 BUILD_TKAGG =3D 0
 BUILD_WXAGG =3D 0
 BUILD_WINDOWING =3D 0
(2) The following code was used to generate the picture:
 import matplotlib
 matplotlib.use("Agg")
 from pylab import *
 from matplotlib.dates import DayLocator, WeekdayLocator, DateFormatter,=
 \
	 date2num
 ...prepare the data...
 rc('xtick',labelsize=3D9)
 rc('ytick',labelsize=3D9)
 figure(figsize=3D(7,5),dpi=3D100)
 axes([0.07, 0.58, 0.89, 0.36])
 ax =3D gca()
 fill(k+k[::-1], xv+xs[::-1], fc=3D"g", ec=3D"g")
 fill(k+[k[-1],k[0]], xs+[0,0], fc=3D"r", ec=3D"r")
 ax.xaxis.set_major_locator(WeekdayLocator(byweekday=3DSU))
 ax.xaxis.set_major_formatter(NullFormatter())
 ax.xaxis.set_minor_locator(DayLocator())
 ax.autoscale_view()
 grid(True)
 axes([0.07, 0.20, 0.89, 0.36])
 ax =3D gca()
 fill(k+k[::-1], yv+ys[::-1], fc=3D"g", ec=3D"g")
 fill(k+[k[-1],k[0]], ys+[0,0], fc=3D"r", ec=3D"r")
 ax.xaxis.set_major_locator(WeekdayLocator(byweekday=3DSU))
 ax.xaxis.set_major_formatter(DateFormatter('%Y-%m-%d'))
 ax.xaxis.set_minor_locator(DayLocator())
 ax.autoscale_view()
 grid(True)
 labels =3D ax.get_xticklabels()
 setp(labels, rotation=3D90)
 savefig("spamdiag.png",dpi=3D100)
(3) You can see the resulting picture at
 http://seehuhn.de/comp/spam.html#fig1
 The problem seems to occur at every second horizontal grid line in
 the lower panel.
Many thanks,
Jochen
--=20
http://seehuhn.de/

Hello Paul,
 thank you very much for your suggestion. I played a little bit with =
the two_scaled.py demo, and it works nicely for 2 different Y-axes. I =
have tried different things in order to have 3 or 4 axes, but it seems =
to me that it is impossible without having 2 axes overlapped. Maybe I am =
missing something...
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.virgilio.it/infinity77 

Hello Andrea,
Have you looked at the file, two_scales.py, in the examples directory? Thi=
s
example would appear to show you how to create plots with two or more scale=
s
per axis.
 -- Paul
On 1/28/06, Andrea Gavana <and...@ti...> wrote:
>
> Hello NG,
>
> please excuse my poor knowledge of matplotlib. I am searching for a
> way
> to do plots with multiple Y axes: for those of you that use Matlab, I am
> looking for something like plotyy and, if it's possible, also something
> more
> complicated like plotyyy or ploty4 (available at Matlab Central File
> Exchange) that allow you to put a third and fourth Y-axis on a plot, like
> in
> this screenshot:
>
>
> http://www.mathworks.de/matlabcentral/fileexchange/util.do?objectId=3D442=
5&imgName=3Dplot4y.png
>
> Is something like this possible with matplotlib? Is there anyone that has
> a
> small example on how to do it?
>
> Thank you in advance for every suggestion.
>
> Andrea.
>
> "Imagination Is The Only Weapon In The War Against Reality."
> http://xoomer.virgilio.it/infinity77
>
>
--
Paul Barrett, PhD Johns Hopkins University
Assoc. Research Scientist Dept of Physics and Astronomy
Phone: 410-516-5190 Baltimore, MD 21218

Hello NG,
 please excuse my poor knowledge of matplotlib. I am searching for a way
to do plots with multiple Y axes: for those of you that use Matlab, I am
looking for something like plotyy and, if it's possible, also something more
complicated like plotyyy or ploty4 (available at Matlab Central File
Exchange) that allow you to put a third and fourth Y-axis on a plot, like in
this screenshot:
http://www.mathworks.de/matlabcentral/fileexchange/util.do?objectId=4425&imgName=plot4y.png
Is something like this possible with matplotlib? Is there anyone that has a
small example on how to do it?
Thank you in advance for every suggestion.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.virgilio.it/infinity77

On Friday 27 January 2006 06:58, Nils Wagner wrote:
> Is it possible to disable this message when importing matplotlib ?
>
> >>> import matplotlib
>
> /usr/lib64/python2.4/site-packages/matplotlib/__init__.py:729:
> UserWarning: ghostscript-8.15 found. ghostscript-8.16 or later is
> recommended for use with the text.usetex option.
> warnings.warn( 'ghostscript-%s found. ghostscript-%s or later is \
This is fixed in cvs. The report can be enabled by setting 
verbose.level=helpful in matplotlibrc.