Hi,
I am still getting crashes using the WX backend with the latest SVN.
For example:
In [1]: figure()
Traceback (most recent call last):
File
"/usr/lib/python2.5/site-packages/matplotlib/backends/backend_wx.py",
line 1092, in _onSize
Hi,
On Thu, 2008-07-24 at 13:08 -0700,
[EMAIL PROTECTED] wrote:
> WARNING:
> /home/jdhunter/dev/lib64/python2.5/site-packages/matplotlib/axes.py:docstring
> of matplotlib.axes.Axes.acorr:36: (ERROR/3) Unexpected indentation.
> WARNING: :0: (ERROR/3) Unexpected indentation.
> WARNING:
> /home/jdh
Hi all,
Is there a way to use
title(r'$ M= I_3 K=\left[\begin{array}{rrr} 2\,k & -k & 0
\\ -k & 2\,k+p & -(k+p) \\ 0 & -(k+p) &
k+p\end{array}\right]$')
It currently fails with
Exception in Tkinter callback
Traceback (most recent call last):
File
"/data/home/nwagner/local/lib/python2.5/li
Hi,
I just noticed a bug in twinx/twiny in axes.py. twinx has:
ax2 = self.figure.add_axes(self.get_position(True), # sharex=self,
frameon=False)
while twiny has:
ax2 = self.figure.add_axes(self.get_position(True), sharey=self,
frameon=False)
Therefore t
On Thu, Jul 24, 2008 at 6:12 PM, Tony Yu <[EMAIL PROTECTED]> wrote:
> I noticed a couple of really minor typos as shown below:
Thanks Tony, committed to 5873
-
This SF.Net email is sponsored by the Moblin Your Move Developer'
Hi,
Attached are two patch sets for you to review and comment on. I am not
intending for these to go in this release.
One is the beginning of a patch set that lets you choose whether text
rotation angle is with respect to screen or axes coordinates. The idea
is that you might want text that is
On Fri, Jul 25, 2008 at 2:48 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Thu, 2008-07-24 at 13:08 -0700,
> [EMAIL PROTECTED] wrote:
>> WARNING:
>> /home/jdhunter/dev/lib64/python2.5/site-packages/matplotlib/axes.py:docstring
>> of matplotlib.axes.Axes.acorr:36: (ERROR/3) Unexpected in
Hi John,
On Thu, Jul 24, 2008 at 21:17, John Hunter <[EMAIL PROTECTED]> wrote:
> I'd like to try and get 98.3 and 91.5 out tomorrow or Saturday -- if
> the weekday doesn't work for you Charlie we might do a source release
> on Friday or Saturday (for Sandro/debian) and you can get the build
As us
On Fri, Jul 25, 2008 at 5:23 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> I have committed to SVN the change making twinx work like twiny. As an
> aside, this would not be necessary if there was an easy after the fact
> way of sharing and unsharing axes (i.e., ax.set_shared_x_axes(ax2)).
Yes, t
On Fri, Jul 25, 2008 at 10:42 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
> Thanks! i've just downlaoded: is 55M tarball the real intended size?
> it seems a little too big... ;)
Argg, I forgot to svn clean before I did the sdist. Please try again.
http://matplotlib.sourceforge.net/tmp/matplot
On Fri, Jul 25, 2008 at 10:09 AM, John Hunter <[EMAIL PROTECTED]> wrote:
> The problem is after the double colon in the following block::
David, I cleaned up a few more of these warnings. I notice on most of
the functions you added to cbook, you added call signature lines, in
many cases where th
David Kaplan wrote:
> The second patch is to pyplot.py to create a plotyy function. This is
> like a matlab function of the same name that puts two curves with
> different y ranges on the same x axis. It basically wraps the
> two_scales.py demo functionality with a bit of extra stuff. I had to
>
Hi,
In my attempt to get scroll wheel zooming working for this release I added
support for the scroll wheel to TkAgg, and added support for draw_idle to
the wx backend.
I'm attaching the wheel zoom demonstration code. This is standalone code
which is not yet ready to go into backend_bases. It o
On Fri, Jul 25, 2008 at 18:37, John Hunter <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 25, 2008 at 10:42 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
>
>> Thanks! i've just downlaoded: is 55M tarball the real intended size?
>> it seems a little too big... ;)
>
> Argg, I forgot to svn clean before I did
Eric Firing wrote:
> John Hunter wrote:
>> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> What else is confusing is how that relates to DPI. When I change the
>>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger*
>>> barbs.
>>> To me, if I'm actua
Hi,
I commited a fixto the axis contains methods, and now have working scroll
wheel zooming code. I still need to use transforms properly before it can
go into matplotlib, so for now I provide it only for demonstration
purposes.
- Paul
import math
import matplotlib
#matplotlib.use('WxAg
John Hunter wrote:
> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> What else is confusing is how that relates to DPI. When I change the
>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger* barbs.
>> To me, if I'm actually specifying pixels, there's
On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
> _print_ps()):
>
>self.figure.set_dpi(72) # Override the dpi kwarg
>dpi = kwargs.get("dpi", 72)
>
> The problem here is that while it sets t
On Fri, Jul 25, 2008 at 5:32 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I commited a fixto the axis contains methods, and now have working scroll
> wheel zooming code. I still need to use transforms properly before it can
> go into matplotlib, so for now I provide it only for demonstrat
Ryan May wrote:
> John Hunter wrote:
>> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> What else is confusing is how that relates to DPI. When I change the
>>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger*
>>> barbs.
>>> To me, if I'm actually
John Hunter wrote:
> On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
>> _print_ps()):
>>
>>self.figure.set_dpi(72) # Override the dpi kwarg
>>dpi = kwargs.get("dpi", 72)
>>
>> The proble
[EMAIL PROTECTED] wrote:
> Revision: 5881
> http://matplotlib.svn.sourceforge.net/matplotlib/?rev=5881&view=rev
> Author: jdh2358
> Date: 2008-07-25 23:54:37 + (Fri, 25 Jul 2008)
>
> Log Message:
> ---
> added set_figure method for quiverkey
>
> Modified Paths:
> -
On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> This is the kind of thing I would want to look at and test *very* carefully,
> or know that someone like John or Mike has done so--which perhaps one of
> them can do quickly. I have looked at this dpi business with puzzleme
John Hunter wrote:
> On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
>> _print_ps()):
>>
>>self.figure.set_dpi(72) # Override the dpi kwarg
>>dpi = kwargs.get("dpi", 72)
>>
>> The proble
On Fri, Jul 25, 2008 at 7:02 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> This looks incomplete--shouldn't the QuiverKey initializer be using this
> function to set the figure from Q.ax.figure, and then should be using
> self.figure to get the transform?
>
> I don't want to jump in if you are in t
On Fri, Jul 25, 2008 at 7:11 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> try:
>from hashlib import md5
> except ImportError:
>from md5 import md5
Looks good to me -- thanks for the offer to fix this. In general, we
only actively want to be supporting 2 python versions at a time, but
if the
John Hunter wrote:
> On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> This is the kind of thing I would want to look at and test *very* carefully,
>> or know that someone like John or Mike has done so--which perhaps one of
>> them can do quickly. I have looked at this
John Hunter wrote:
> On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> This is the kind of thing I would want to look at and test *very* carefully,
>> or know that someone like John or Mike has done so--which perhaps one of
>> them can do quickly. I have looked at this
Hi,
I fixed some of the contains() methods so at least the simple
cases work.
Degenerate rectangles cause problems in axes_demo:
>>> import matplotlib.patches
>>> r = matplotlib.patches.Rectangle((0,0),1,0)
>>> r.get_transform().inverted()
Traceback (most recent call last):
File "", line 1,
John Hunter wrote:
> On Fri, Jul 25, 2008 at 7:02 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> This looks incomplete--shouldn't the QuiverKey initializer be using this
>> function to set the figure from Q.ax.figure, and then should be using
>> self.figure to get the transform?
>>
>> I don't wan
30 matches
Mail list logo
