matplotlib-devel Mailing List for matplotlib

Hi all,
As per the feedback I received from some of you, I am releasing the next 
version of WebLab with MIT license. Also in the new release are more demo 
files as well as new GUI toolkit.
http://www.physics.ox.ac.uk/users/santoso/Software.WebLab.html
Thanks for the feedback :)
Best regards,
Yusdi
_________________________________________________________________
Interest Rates NEAR 39yr LOWS! 430,000ドル Mortgage for 1,299ドル/mo - Calculate 
new payment 
http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-19132&moid=14888

Hi Edin,
Thanks for the message. In fact I had some emails from André Roberge from 
crunchy about possible collaboration. We'll see how things transpire :)
Yusdi
>From: "Edin Salkovic" <edi...@gm...>
>Hi Yusdi,
>
>Great stuff!
>
>I'm working this year on a Google Summer of Code project related to
>crunchy (Interactive Python tutorials served through a web browser):
>http://code.google.com/p/crunchy/
>
>and part of the project is developing a plugin for seamlessly
>integrating matplotlib (and other image generating python libraries)
>into it, so I'll keep an eye on WebLab.
>
>Edin
_________________________________________________________________
Mortgage refinance is Hot. *Terms. Get a 5.375%* fix rate. Check savings 
https://www2.nextag.com/goto.jsp?product=100000035&url=%2fst.jsp&tm=y&search=mortgage_text_links_88_h2bbb&disc=y&vers=925&s=4056&p=5117

On 4/19/07, Yusdi Santoso <yu...@ho...> wrote:
> Hi all,
>
> I'm not sure if this is the right mailing list for this, so please bear with
> me if this is not for you.
>
> I have developed a web front end for matplotlib, rather inspired by matlab
> development environment. You can find more of the details here:
> http://www.physics.ox.ac.uk/users/santoso/Software.WebLab.html
Hi Yusdi,
Great stuff!
I'm working this year on a Google Summer of Code project related to
crunchy (Interactive Python tutorials served through a web browser):
http://code.google.com/p/crunchy/
and part of the project is developing a plugin for seamlessly
integrating matplotlib (and other image generating python libraries)
into it, so I'll keep an eye on WebLab.
Edin

On 4/20/07, Yusdi Santoso <yu...@ho...> wrote:
> Hi Glen,
>
> Thanks for the pointer. I am not really particular or savy about licenses, I
> just happened to pick LGPL just because I though that it will be the most
> flexible. I suppose I could just release the next version with another
> license.
That would be great: if you licensed it BSD, then both matplotlib and
ipython could directly benefit from your code. As it stands, neither
of us can touch your code, and what you are doing meshes very well
where the ipython development is moving, so we'd be thrilled to
collaborate with you. But as long as your code remains *GPL, we can't
approach it.
Thanks for considering this.
Cheers,
f

Hi Glen,
Thanks for the pointer. I am not really particular or savy about licenses, I 
just happened to pick LGPL just because I though that it will be the most 
flexible. I suppose I could just release the next version with another 
license.
Thanks again.
Yusdi
_________________________________________________________________
Don’t quit your job – Take Classes Online and Earn your Degree in 1 year. 
Start Today! 
http://www.classesusa.com/clickcount.cfm?id=866146&goto=http%3A%2F%2Fwww.classesusa.com%2Ffeaturedschools%2Fonlinedegreesmp%2Fform-dyn1.html%3Fsplovr%3D866144

Hi Nils,
It was originally developed in Linux, but I don't have any more time now to 
cross check it in Linux, but I should think it would work out of the box (or 
with minor modification). It will be great if you can give it a try :)
Thanks,
Yusdi
_________________________________________________________________
MSN is giving away a trip to Vegas to see Elton John. Enter to win today. 
http://msnconcertcontest.com?icid-nceltontagline

On Wed, Apr 18, 2007 at 03:10:54PM -0700, Yusdi Santoso wrote:
> I'm not sure if this is the right mailing list for this, so please bear with 
> me if this is not for you.
> 
> I have developed a web front end for matplotlib, rather inspired by matlab 
> development environment. You can find more of the details here:
> http://www.physics.ox.ac.uk/users/santoso/Software.WebLab.html
> 
> It is usable right now although with some known problem especially in the 
> area of secure code execution.
> Any comments will be greatly appreciated.
Yusdi,
weblab looks like a really awesome project.
I haven't installed it yet, but I noticed that you released it LGPL.
Did you by chance already take into account this page?
http://www.scipy.org/License_Compatibility
Glen

Hi all,
I'm not sure if this is the right mailing list for this, so please bear with 
me if this is not for you.
I have developed a web front end for matplotlib, rather inspired by matlab 
development environment. You can find more of the details here:
http://www.physics.ox.ac.uk/users/santoso/Software.WebLab.html
It is usable right now although with some known problem especially in the 
area of secure code execution.
Any comments will be greatly appreciated.
Thanks and best regards,
Yusdi
_________________________________________________________________
Mortgage refinance is Hot. *Terms. Get a 5.375%* fix rate. Check savings 
https://www2.nextag.com/goto.jsp?product=100000035&url=%2fst.jsp&tm=y&search=mortgage_text_links_88_h2bbb&disc=y&vers=925&s=4056&p=5117

Manuel,
Thanks very much. I have applied your patch.
Eric
Manuel Metz wrote:
> Dear all,
> some time ago (October last year) I mailed a patch for a bug in
> backend_agg.py which is still not included. I attached the patch against
> the latest SVN again.
> The problem seems to be a missing parameter when calling the function
> draw_ellipse.
> 
> Manuel
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Index: backend_agg.py
> ===================================================================
> --- backend_agg.py	(revision 3243)
> +++ backend_agg.py	(working copy)
> @@ -172,8 +172,8 @@
> if __debug__: verbose.report('RendererAgg.draw_point', 'debug-annoying')
> rgbFace = gc.get_rgb()
> self._renderer.draw_ellipse(
> - gc, rgbFace, x, y, 0.5, 0.5)
> -
> + gc, rgbFace, x, y, 0.5, 0.5, 0.0)
> + 
> def draw_mathtext(self, gc, x, y, s, prop, angle):
> """
> Draw the math text using matplotlib.mathtext
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> 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-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Fixed. Try again.
> -----Original Message-----
> From: Eric Firing [mailto:ef...@ha...]
> Sent: Wednesday, April 18, 2007 12:22 AM
> To: James Evans
> Cc: matplotlib development list
> Subject: R3237 breaks mri_with_eeg.py demo
> 
> Revision 3237 to fix set_ticklabels seems to have a problem: it breaks
> examples/mri_with_eeg.py.
> 
> Eric

dGhlIHNhbWUgcHJvYmxlbS4KVGVtcG9yYXJ5IHNvbHV0aW9uIGlzIHRvIHNldCBzZWNvbmQgdHVw
bGUgdmFsdWVzIHRvIG5vbnplcm8gKDAuMDAwMSBmb3IKZXhhbXBsZSkgYmVmb3JlIHBhc3Npbmcg
aXQgaW50byBzZXFfeHlfdHVwcywgYnV0IGl0IGlzIHZlcnkgX2RpcnR5Xy4KCkdvdCB2ZXJzaW9u
IDAuOTAuMCBpbnN0YWxsZWQgZnJvbSBzb3VyY2UgKGxhdGVzdCBLdWJ1bnR1KS4KSi4KCk9uIDE4
LzA0LzA3LCBKb3VuaSBLLiBTZXBww6RuZW4gPGprc0Bpa2kuZmk+IHdyb3RlOgo+Cj4gIkppxZnD
rSBQb3BlayIgPGppcmkucG9wZWtAZ21haWwuY29tPiB3cml0ZXM6Cj4KPiA+IGFueXRpbWUgd2hl
biByZXF1ZXN0aW5nIHNlbWlsb2d5KCkgb24gYmFyIG9yIGhpc3QgY2hhcnQsIGZvbGxvd2luZyBl
cnJvcgo+ID4gb2NjdXJzOgo+Cj4gSG93IGFib3V0IGJhciguLi4sIGxvZz1UcnVlKSBvciBoaXN0
KC4uLiwgbG9nPVRydWUpPwo+Cj4gLS0KPiBKb3VuaSBLLiBTZXBww6RuZW4KPiBodHRwOi8vd3d3
LmlraS5maS9qa3MKPgo+Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IFRoaXMgU0YubmV0IGVtYWlsIGlz
IHNwb25zb3JlZCBieSBEQjIgRXhwcmVzcwo+IERvd25sb2FkIERCMiBFeHByZXNzIEMgLSB0aGUg
RlJFRSB2ZXJzaW9uIG9mIERCMiBleHByZXNzIGFuZCB0YWtlCj4gY29udHJvbCBvZiB5b3VyIFhN
TC4gTm8gbGltaXRzLiBKdXN0IGRhdGEuIENsaWNrIHRvIGdldCBpdCBub3cuCj4gaHR0cDovL3Nv
dXJjZWZvcmdlLm5ldC9wb3dlcmJhci9kYjIvCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18KPiBNYXRwbG90bGliLWRldmVsIG1haWxpbmcgbGlzdAo+IE1h
dHBsb3RsaWItZGV2ZWxAbGlzdHMuc291cmNlZm9yZ2UubmV0Cj4gaHR0cHM6Ly9saXN0cy5zb3Vy
Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vbWF0cGxvdGxpYi1kZXZlbAo+Cg==

"Jiří Popek" <jir...@gm...> writes:
> anytime when requesting semilogy() on bar or hist chart, following error
> occurs:
How about bar(..., log=True) or hist(..., log=True)?
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi all,
anytime when requesting semilogy() on bar or hist chart, following error
occurs:
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/backends/backend_qtagg.py", line 161,
in print_figure
 **kwargs )
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/backends/backend_agg.py", line 456,
in print_figure
 self.draw()
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/backends/backend_agg.py", line 392,
in draw
 self.figure.draw(renderer)
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/figure.py", line 569, in draw
 for a in self.axes: a.draw(renderer)
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/axes.py", line 1155, in draw
 a.draw(renderer)
 File "/usr/lib/python2.5/site-packages/matplotlib-
0.90.0-py2.5-linux-i686.egg/matplotlib/patches.py", line 215, in draw
 tverts = self.get_transform().seq_xy_tups(verts)
ValueError: Cannot take log of nonpositive value
I am sure that there is no negative value (just some zeros - this could be
the problem)
Anybody have an idea how to solve it?

Dear all,
some time ago (October last year) I mailed a patch for a bug in
backend_agg.py which is still not included. I attached the patch against
the latest SVN again.
The problem seems to be a missing parameter when calling the function
draw_ellipse.
Manuel
-- 
---------------------------------------
 Manuel Metz ............ Stw@AIfA
 Argelander Institut fuer Astronomie
 Auf dem Huegel 71 (room 3.06)
 D - 53121 Bonn
 E-Mail: mm...@as...
 Web: www.astro.uni-bonn.de/~mmetz
 Phone: (+49) 228 / 73-3660
 Fax: (+49) 228 / 73-3672
---------------------------------------

Revision 3237 to fix set_ticklabels seems to have a problem: it breaks 
examples/mri_with_eeg.py.
Eric

Michael Fitzgerald wrote:
> Hi all,
> 
> I found a small bug, where Figure.clf() was erroneously leaving some axes 
> instances in the Figure.axes list. It turns out the method was deleting 
> items from the list while iterating over it. Attached is a patch.
> 
> Mike
> 
Mike,
Thanks for finding that rather subtle bug. I committed an equivalent 
change; I used tuple(self.axes) instead of copy.copy(self.axes) because 
for this purpose it accomplishes the same thing, but faster, and without 
the extra import.
Eric
> 
> 
> ------------------------------------------------------------------------
> 
> Index: figure.py
> ===================================================================
> --- figure.py	(revision 3198)
> +++ figure.py	(working copy)
> @@ -1,7 +1,7 @@
> """
> Figure class -- add docstring here!
> """
> -import sys
> +import sys, copy
> import artist
> from artist import Artist
> from axes import Axes, Subplot, PolarSubplot, PolarAxes
> @@ -515,7 +515,7 @@
> """
> Clear the figure
> """
> - for ax in self.axes:
> + for ax in copy.copy(self.axes):
> ax.cla()
> self.delaxes(ax)
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi all,
I found a small bug, where Figure.clf() was erroneously leaving some axes 
instances in the Figure.axes list. It turns out the method was deleting 
items from the list while iterating over it. Attached is a patch.
Mike

I'd personally be happy to move on to wxPython 2.8 but I'm using
enthought's matplotlib egg, which apparently requires enthought's
wxPython egg, and that's still at version 2.6.
--bb
On 4/12/07, Christopher Barker <Chr...@no...> wrote:
> Hi all,
>
> The world of wxAgg and versions of wxPython has been a big pain for a
> while. I've been poking around trying to get MPL working with wxPython
> on OS-X with wxPython2.8, and it's been far too much work.
>
> However, Ken McIvor has apparently solved the problem. Unfortunately, he
> committed the changes on Feb 22, and it looks like the 0.90.0 release
> was done on Feb 6. Darn.
>
> My understanding of the changes is:
>
> There is now code in backend_wxagg.py that uses methods to create and
> manipulate wx.Bitmaps that is new to wxPython2.8. This should make the
> old accelerator code obsolete.
>
> At runtime, the code determines if you are running >2.8, and if so, uses
> the new code. If not, it reverts to the old code, which checks for the
> accelerator, uses it if it's there, and uses the pure-python
> non-accelerated code if not.
>
> So -- this should allow one to build a single executable that will work
> well with wxPython 2.6, 2.8 and future wxPythons.
>
> Personally, I think we should just drop the accelerator altogether. If
> someone needs better performance, let them use wxPython2.8 ( I think
> there is some room for improvement in the pre-2.8 python code too -- you
> could build the wxImage from a buffer, rather than a string, saving one
> data copy).
>
> If the accelerator is dropped, then the whole build process gets easier.
>
> If people want to keep the accelerator, I wrote some code for
> setup_ext.py that checks what version of wx you have installed, and
> finds the wx-config that matches it. It could be adapted a bit to try to
> build only a wxPython2.6 version, and not try to build a 2.8 version,
> which fails at this point.
>
> So, with a bit more testing and tweaking, we could get this all settled.
>
> What's the consensus on keeping the accelerator?
>
> Is it worth putting out a point release with these fixes?
>
>
> -Chris
>
>
>
> --
> 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...
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi all,
The world of wxAgg and versions of wxPython has been a big pain for a 
while. I've been poking around trying to get MPL working with wxPython 
on OS-X with wxPython2.8, and it's been far too much work.
However, Ken McIvor has apparently solved the problem. Unfortunately, he 
committed the changes on Feb 22, and it looks like the 0.90.0 release 
was done on Feb 6. Darn.
My understanding of the changes is:
There is now code in backend_wxagg.py that uses methods to create and 
manipulate wx.Bitmaps that is new to wxPython2.8. This should make the 
old accelerator code obsolete.
At runtime, the code determines if you are running >2.8, and if so, uses 
the new code. If not, it reverts to the old code, which checks for the 
accelerator, uses it if it's there, and uses the pure-python 
non-accelerated code if not.
So -- this should allow one to build a single executable that will work 
well with wxPython 2.6, 2.8 and future wxPythons.
Personally, I think we should just drop the accelerator altogether. If 
someone needs better performance, let them use wxPython2.8 ( I think 
there is some room for improvement in the pre-2.8 python code too -- you 
could build the wxImage from a buffer, rather than a string, saving one 
data copy).
If the accelerator is dropped, then the whole build process gets easier.
If people want to keep the accelerator, I wrote some code for 
setup_ext.py that checks what version of wx you have installed, and 
finds the wx-config that matches it. It could be adapted a bit to try to 
build only a wxPython2.6 version, and not try to build a 2.8 version, 
which fails at this point.
So, with a bit more testing and tweaking, we could get this all settled.
What's the consensus on keeping the accelerator?
Is it worth putting out a point release with these fixes?
-Chris
-- 
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...

Timothy <te...@xm...> writes:
> It appears matplotlib does not have a dendrogram plot. I may be 
> interested in developing one, if I can get a sense for what it would 
> take. Could someone suggest some code I could look at as a model for 
> developing a new plot?
In the file axes.py, search for the comment "Specialized plotting" and
look at the functions after that. The first function is "bar", which
looks quite complicated, but perhaps "stem" would be a good starting
point.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

It appears matplotlib does not have a dendrogram plot. I may be 
interested in developing one, if I can get a sense for what it would 
take. Could someone suggest some code I could look at as a model for 
developing a new plot?
Thanks,
--Tim

On 4/10/07, Tim Leslie <tim...@gm...> wrote:
> Here's another patch. This one cleans up the line2d_seg_dist function
> and also speeds it up by a factor of ~2
Excellent, thanks.
Committed.
JDH

On 4/10/07, Darren Dale <dd...@co...> wrote:
> I don't understand how that could have happened. I've been using qt4agg for a
> long time, and have never had trouble with the save button until now.
Could be only triggered by a particular rc file setup, but we did see
the problem.
Cheers,
f

On Tuesday 10 April 2007 01:49:22 pm Fernando Perez wrote:
> Hi all,
>
> just a heads-up since I normally don't mess with the actual repo. I
> just committed
>
> planck[backends]> svn diff backend_qt4agg.py
> Index: backend_qt4agg.py
> ===================================================================
> --- backend_qt4agg.py (revision 3201)
> +++ backend_qt4agg.py (working copy)
> @@ -4,6 +4,8 @@
> from __future__ import division
>
> import os, sys
> +
> +import matplotlib
> from matplotlib import verbose
> from matplotlib.cbook import enumerate
> from matplotlib.figure import Figure
>
>
> as r3202.
>
> That missing import would cause all kinds of problems, including the
> 'save' button in the GUI not working at all.
>
> John: unfortunately it's too late to propagate these changes to the
> lab, I'm afraid (as trivial as they are).
I don't understand how that could have happened. I've been using qt4agg for a 
long time, and have never had trouble with the save button until now.
Darren

Hi all,
just a heads-up since I normally don't mess with the actual repo. I
just committed
planck[backends]> svn diff backend_qt4agg.py
Index: backend_qt4agg.py
===================================================================
--- backend_qt4agg.py (revision 3201)
+++ backend_qt4agg.py (working copy)
@@ -4,6 +4,8 @@
 from __future__ import division
 import os, sys
+
+import matplotlib
 from matplotlib import verbose
 from matplotlib.cbook import enumerate
 from matplotlib.figure import Figure
as r3202.
That missing import would cause all kinds of problems, including the
'save' button in the GUI not working at all.
John: unfortunately it's too late to propagate these changes to the
lab, I'm afraid (as trivial as they are).
Cheers,
f