matplotlib-devel Mailing List for matplotlib

Hi everybody,
I just found your application, and I'm stunned. You've done a great job. 
I'm the lead developer of another application called SciGraphica 
(http://scigraphica.sourceforge.net) and GtkExtra, a package of widgets 
for (among other things) plotting 2d, contour, 3d, and polar plots. 
SciGraphica is built on top of gtkextra and it's not competing with 
matplot in the sense that it aims at having a GUI based program ala 
Microcal Origin, with spreadsheets for editing and manipulating the 
data. I hope you agree that we can learn from each others experiences 
with algorithms, etc. This is precisely why I'm contacting you, guys!
I have to confess that my contour and 3d plots are pretty "raw" in the 
sense that the algorithms I use are quite primitive and slow. I basicaly 
generate a delaunay triangulation and cut the triangles with planes, and 
draw the resulting polygons. I was wondering if you guys could give me 
some feedback about a good algorithm for plotting 2d contour plots, or 
at least, tell me where to look in your code to see if I can learn from 
it. Whare are the actual engines to plot the pie charts and contours, 
for instance?
I hope you guys don't mind sharing info with me, actually this is one of 
the reasons for doing OSS. I hope we can enjoy a fruitful communication. 
All the best, and congratulations again for your project.
Saludos,
<ADRIAN>
PS: If by any chance you feel inclined to trying SG, I suggest you to go 
directly for the CVS code, since the latest release is not very stable.

John Hunter wrote:
>>>>>>"Fernando" == Fernando Perez <Fer...@co...> writes:
> 
> 
> Fernando> Stephen Walton wrote:
> >> Fernando Perez wrote:
> >>> Well, it could be something like $HOME/.tex.cache, where $HOME
> >>> can be determined via a routine like the below (this is what
> >>> ipython uses to try and guess a sensible value for $HOME):
> >> I *like* it.
> 
> Fernando> Though I'd personally vote for matplotlib holding
> Fernando> $HOME/.matplotlib/ as a directory, and putting in there
> Fernando> a tex.cache dir, the matplotlibrc file, and anything
> Fernando> else it may need in the future.
> 
> I am in the process of moving all of matplotlib's config files and
> outputs to HOME/.matplotlib.
Great!
> what I am really after is a simple print >> sys.stderr. Is there
> anything wrong with using sys.stderr for this kind of thing, error
> mavens? I know when we discussed this many moons ago we converged on
> using exceptions and the warnings module everywhere. But now I am a
> bit confounded by the inability to make the warnings print pretty
> messages that the typical user will read and understand. Or is there
> a way to tell warning.warn to just print the error message with no
> lineno/traceback info?
Dunno, sorry. In ipython, I have a trivial warn() routine which is just a 
print >> sys.stderr wrapper. I've never used the stdlib's warnings module.
Cheers,
f

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:
 Fernando> Stephen Walton wrote:
 >> Fernando Perez wrote:
 >>> Well, it could be something like $HOME/.tex.cache, where $HOME
 >>> can be determined via a routine like the below (this is what
 >>> ipython uses to try and guess a sensible value for $HOME):
 >> I *like* it.
 Fernando> Though I'd personally vote for matplotlib holding
 Fernando> $HOME/.matplotlib/ as a directory, and putting in there
 Fernando> a tex.cache dir, the matplotlibrc file, and anything
 Fernando> else it may need in the future.
I am in the process of moving all of matplotlib's config files and
outputs to HOME/.matplotlib.
I want to issue a warning to users if I find a .matplotlibrc file (the
new name is matplotlibrc (no hidden "dot") and the default location is
HOME/.matplotlib/matplotlibrc. As before, you can put an rc file in
the current dir.
I am using warnings.warn to issue the warning
 home = get_home()
 oldname = os.path.join( home, '.matplotlibrc')
 if os.path.exists(oldname):
 warnings.warn('Old rc filename "%s" found and ignored; new default rc file name is HOME/.matplotlib/matplotlibrc"'%oldname)
But this results in a warning that looks like this
 > python ~/python/projects/matplotlib/examples/subplot_demo.py
 /usr/lib/python2.4/site-packages/matplotlib/__init__.py:737: UserWarning: Old rc filename "/home/jdhunter/.matplotlibrc" found and ignored; new default rc file name is HOME/.matplotlib/matplotlibrc"
 warnings.warn('Old rc filename "%s" found and ignored; new default rc file name is HOME/.matplotlib/matplotlibrc"'%oldname)
which I find hard to read. I can add a stacklevel=0 argument to warn
which is slightly more legible
 > python ~/python/projects/matplotlib/examples/subplot_demo.py
 /usr/lib/python2.4/warnings.py:41: UserWarning: Old rc filename "/home/jdhunter/.matplotlibrc" found and ignored; new default rc file name is HOME/.matplotlib/matplotlibrc"
 lineno = caller.f_lineno 
but still has the annoying "lineno = caller.f_lineno"
what I am really after is a simple print >> sys.stderr. Is there
anything wrong with using sys.stderr for this kind of thing, error
mavens? I know when we discussed this many moons ago we converged on
using exceptions and the warnings module everywhere. But now I am a
bit confounded by the inability to make the warnings print pretty
messages that the typical user will read and understand. Or is there
a way to tell warning.warn to just print the error message with no
lineno/traceback info?
JDH