Hi,
On Fri, 2008-07-25 at 12:43 -0500, John Hunter wrote:
> Also, I would rather not put the geometry functions in cbook, eg
> distances_along_curve and path_length and friends. Perhaps we should
> have some sort of geometry module where all these things live (there
> are some in mlab as well) bu
On Sat, Jul 26, 2008 at 7:19 AM, David M. Kaplan <[EMAIL PROTECTED]> wrote:
> I started looking at this reorganization, but it seems to me that mlab
> already has a number of functions that don't seem to have much to do
> with its initial purpose - matlab compatibility. This was pretty
> confusin
On Fri, Jul 25, 2008 at 4:12 PM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
> 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?
>>>
I just fixed a small bug when bins were not filled and C was specified.
Attached is the revised version.
Index: lib/matplotlib/axes.py
===
--- lib/matplotlib/axes.py (revision 5892)
+++ lib/matplotlib/axes.py (working copy)
@@ -4941,24
On Sat, Jul 26, 2008 at 3:37 PM, Andrew Straw <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've added some functionality to my copy hexbin, and I thought I'd
> bounce it off folks (esp. Michael) to see if it seems like a good idea
> to add it to MPL.
Do you mean Michiel, the hexbin author? I m CC-ing
Hi,
I went through all the demos in pylab_examples to make sure that
the artist.contains() method would return true when the mouse
is on the object. I fixed a number of problems caused by the
new transforms code (collections, lines and images were not
detected). A few issues remain, but they are
Andrew Straw wrote:
> Hi all,
>
> I've added some functionality to my copy hexbin, and I thought I'd
> bounce it off folks (esp. Michael) to see if it seems like a good idea
> to add it to MPL.
>
> Here's the beginning of the docstring of the new version. What I've
> added is the optional argumen
On Sat, Jul 26, 2008 at 5:26 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> I went through all the demos in pylab_examples to make sure that
> the artist.contains() method would return true when the mouse
> is on the object. I fixed a number of problems caused by the
> new transforms code (collect
Eric Firing wrote:
> Andrew Straw wrote:
>> Hi all,
>>
>> I've added some functionality to my copy hexbin, and I thought I'd
>> bounce it off folks (esp. Michael) to see if it seems like a good idea
>> to add it to MPL.
>>
>> Here's the beginning of the docstring of the new version. What I've
>> ad
The attached script gives a quick and simple illustration of the pdf
backend memory leak noted earlier by Paul Kienzle. It seems to be
entirely related to rendering text. Adding axes, lines, and images does
not seem to matter, except insofar as adding an axes will trigger the
rendering of tex
Paul Kienzle wrote:
> Hi,
>
> I went through all the demos in pylab_examples to make sure that
> the artist.contains() method would return true when the mouse
> is on the object. I fixed a number of problems caused by the
> new transforms code (collections, lines and images were not
> detected).
On Sat, Jul 26, 2008 at 7:20 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> The attached script gives a quick and simple illustration of the pdf backend
> memory leak noted earlier by Paul Kienzle. It seems to be entirely related
> to rendering text. Adding axes, lines, and images does not seem to
John Hunter wrote:
> On Sat, Jul 26, 2008 at 7:20 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> The attached script gives a quick and simple illustration of the pdf backend
>> memory leak noted earlier by Paul Kienzle. It seems to be entirely related
>> to rendering text. Adding axes, lines, a
13 matches
Mail list logo
