I forgot to attach the patch.
-JJ
On Fri, Jul 25, 2008 at 2:39 AM, Jae-Joon Lee <[EMAIL PROTECTED]> wrote:
> Hi,
>
> While playing a little bit with "custom_projection_example.py", I
> found that "plot" command with projection="hammer" plots too many
> markers.
>
> For example,
>
>subplot(11
Hi,
While playing a little bit with "custom_projection_example.py", I
found that "plot" command with projection="hammer" plots too many
markers.
For example,
subplot(111, projection="hammer")
grid(True)
p = plot([-1, 1, 1], [-1, -1, 1], "o")
show()
plots more than 100 circles, i
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
Ryan May wrote:
> Hi,
>
> This is probably best directed to Eric, but to anyone who knows how
> quiver works with regard to units: QuiverKey right now is failing if
> coordinates="inches". There are a couple of non-defined variables
> accesses in there, and it just doesn't look right. The off
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 no way that they should
>
Eric Firing wrote:
> John Hunter wrote:
>> On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> Ok, it fixes the problem if I pass dpi=72 to savefig().
>>> Curiously,
>>> passing dpi=72 to Figure() does not have the same effect. So now how
>>> do I
>>
>> That is because
Hi,
This is probably best directed to Eric, but to anyone who knows how
quiver works with regard to units: QuiverKey right now is failing if
coordinates="inches". There are a couple of non-defined variables
accesses in there, and it just doesn't look right. The offending part
of the if chain
Eric Firing wrote:
>> Anyone have any ideas?
>
> I don't, but it appears that the set_clip_path method was introduced in
> 4817 by Mike D., complete with the commented-out lines.
> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/lib/matplotlib/axis.py?annotate=5651
>
>
David Kaplan wrote:
>> * Using an empty list in a python kwarg as the default is a gotcha, as in
>>
>> def calc_label_rot_and_inline( self, slc, ind, lw, lc=[], spacing=5 ):
>>
>> The reason is that if the function mutates the list, this often leads
>> to unintended consequences as the list is
On Thu, Jul 24, 2008 at 12:25 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> canvas interface for interactive plotting applications
The Chaco devs (in particular Peter Wang) will be there, so it would
be worthwhile having a detailed conversation with him on this matter,
as this is definitely Chac
Paul Kienzle wrote:
> Hi,
>
> I added support for scroll wheel events in wx. This includes
> a new attribute event.step since the wx mouse wheel event
> reports larger steps when scrolling faster. I don't see
> how to check step in gtk, so I set step to +1 and -1 for up
> and down.
>
> Can som
Paul Kienzle wrote:
> Hello,
>
> Anyone planning to attend post-SciPy2008 code sprints?
>
> Some projects I'm interested in:
>
> support for units (px, pt/in/cm/mm, em/ex/, %axis/%figure)
> style sheet editor (needs backend support for forms and menus)
> canvas interface for interactive pl
Eric Firing wrote:
> Ryan May wrote:
>> Hey,
>>
>> I noticed today, while working on my skewT, that you can't tell the
>> axis objects to clip their ticklines. If you want to set clipping on
>> each individual tickline. I saw that the code is there in the
>> relevant classes, but the lines to s
Ryan May wrote:
> Hey,
>
> I noticed today, while working on my skewT, that you can't tell the axis
> objects to clip their ticklines. If you want to set clipping on each
> individual tickline. I saw that the code is there in the relevant
> classes, but the lines to set clipping are disabled i
Hey,
I noticed today, while working on my skewT, that you can't tell the axis
objects to clip their ticklines. If you want to set clipping on each
individual tickline. I saw that the code is there in the relevant
classes, but the lines to set clipping are disabled in set_clip_path()
or _set_a
I noticed a couple of really minor typos as shown below:
Index: matplotlib/lib/matplotlib/axis.py
===
--- matplotlib/lib/matplotlib/axis.py (revision 5860)
+++ matplotlib/lib/matplotlib/axis.py (working copy)
@@ -147,7 +147,7 @@
On Thu, Jul 24, 2008 at 5:45 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I added support for scroll wheel events in wx. This includes
> a new attribute event.step since the wx mouse wheel event
> reports larger steps when scrolling faster. I don't see
> how to check step in gtk, so I se
Hi,
I added support for scroll wheel events in wx. This includes
a new attribute event.step since the wx mouse wheel event
reports larger steps when scrolling faster. I don't see
how to check step in gtk, so I set step to +1 and -1 for up
and down.
Can someone with gtk please run the following
Eric Firing wrote:
> John Hunter wrote:
>> On Thu, Jul 24, 2008 at 4:20 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
>>
>>> Running, I get a leak of about 5.6 KiB per loop.
>>> I'm using matplotlib svn, macos 10.4, numpy 1.1.0
>> I'm not seeing this w/ PDF or Agg in linux... what backend are you
>
On Thu, Jul 24, 2008 at 5:16 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> PDF.
OK, correction, I am seeing this too. I cheated and didn't let the
test run to the end. It looked like the memory was flat-lining so I
moved on the Agg test (which is not leaking on my completed tests).
> The examp
On Thu, Jul 24, 2008 at 04:28:00PM -0500, John Hunter wrote:
> On Thu, Jul 24, 2008 at 4:20 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> > Running, I get a leak of about 5.6 KiB per loop.
> > I'm using matplotlib svn, macos 10.4, numpy 1.1.0
>
> I'm not seeing this w/ PDF or Agg in linux... what
On Thu, Jul 24, 2008 at 4:20 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> I also fixed some of the lesser used examples. I'm not going to try to
> fix examples/units. examples/animation/anim.py doesn't update on my
> wxagg backend (wx 2.8.3).
I fixed a few of the units examples that were trivi
John Hunter wrote:
> On Thu, Jul 24, 2008 at 4:20 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
>
>> Testing hawaii on my machine, I saw the following error:
>>
>> Traceback (most recent call last):
>>File "memleak_hawaii3.py", line 13, in
>> rand = np.mlab.rand
>> AttributeError: 'modul
On Thu, Jul 24, 2008 at 4:20 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> Testing hawaii on my machine, I saw the following error:
>
> Traceback (most recent call last):
>File "memleak_hawaii3.py", line 13, in
> rand = np.mlab.rand
> AttributeError: 'module' object has no attribute 'm
On Thu, Jul 24, 2008 at 02:17:19PM -0500, John Hunter 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
> out over the weekend (i
I am out on town for a meeting until Sunday evening. I unfortunately won't
be able to act until Monday at the earliest. Cutting the source release
sounds like a good plan.
- Charlie
On Thu, Jul 24, 2008 at 3:17 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> I'd like to try and get 98.3 and 91.5
John Hunter wrote:
> On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, it fixes the problem if I pass dpi=72 to savefig(). Curiously,
>> passing dpi=72 to Figure() does not have the same effect. So now how do I
>
> That is because "savefig" has its own dpi, which ov
Hello,
Anyone planning to attend post-SciPy2008 code sprints?
Some projects I'm interested in:
support for units (px, pt/in/cm/mm, em/ex/, %axis/%figure)
style sheet editor (needs backend support for forms and menus)
canvas interface for interactive plotting applications
- Paul
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
out over the weekend (if you have time). Obviously a lot of work has
gone into these releas
There are a number of documentation warnings -- at lease some of these
are because doc strings in the api docs are non-compliant. If you've
been working on any of these functions, please take a moment to try
and bring them up to snuff (I suspect one or more of these is mine,
but I'm pasting them a
On Thu, Jul 24, 2008 at 05:14:42PM +0200, David Kaplan wrote:
> Hi,
>
> No, it doesn't appear to work with or without my changes. Also, it
> looks to me like the following code is now misplaced in backend_wx.py:
>
> # Event binding code changed after version 2.5
> if wx.VERSION_STRING >= '2.5':
Hi,
No, it doesn't appear to work with or without my changes. Also, it
looks to me like the following code is now misplaced in backend_wx.py:
# Event binding code changed after version 2.5
if wx.VERSION_STRING >= '2.5':
def bind(actor,event,action,**kw):
actor.Bind(event,action,**kw)
On Thu, Jul 24, 2008 at 9:32 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
>> * avoid the ternary operator, as in
>>
>> # Figure out label rotation.
>> rotation,nlc = cs.calc_label_rot_and_inline(
>> slc, imin, lw, lc if self.inline else [],
>>
On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Ok, it fixes the problem if I pass dpi=72 to savefig(). Curiously,
> passing dpi=72 to Figure() does not have the same effect. So now how do I
That is because "savefig" has its own dpi, which overrides the figure
dpi. Tee
On Thu, Jul 24, 2008 at 12:12:21PM +0200, David Kaplan wrote:
> 4) In WX, I used the code submitted by Paul, but was unable to check it
> because when I tried to use the WX backend, I got an error about no
> GraphicsContext (below). This looks bad. I am using wxPython: 2.6.3.2.
Does wx work for
Hi,
I made the suggested fixes. Comments below:
On Thu, 2008-07-24 at 08:38 -0500, John Hunter wrote:
> On Thu, Jul 24, 2008 at 7:31 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
>
> > I committed the changes to clabel (r5830).
>
> Hey David -- thanks for these fixes. I noticed a couple of thin
On Thu, Jul 24, 2008 at 7:31 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> I committed the changes to clabel (r5830).
Hey David -- thanks for these fixes. I noticed a couple of things I
want to comment on
* avoid the ternary operator, as in
# Figure out label rotation.
Hi,
I committed the changes to clabel (r5830). For the attribute renaming,
I think we can safely rename most of them. In my opinion, the only ones
that users might use are .cl, .cl_xy and .cl_cvalues. The clabel
function creates these just before finishing from their more
appropriately named ve
Hi,
I have finally committed a changeset for moving the "event loop" stuff
into the backends. I have hopefully found a compromise that will please
most. Since this is close to release date, I suggest that everyone who
can give it a look (r5831) and if there is any problem, just role the
changes
39 matches
Mail list logo
