On Thu, Jul 31, 2008 at 10:37 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Yes, it looks like _ttconv.cpp is the culprit here. Sloppy reference
> handling (and I say that as the author of that file...) I've committed some
> changes to SVN that seem to remove the leaks with memleak_hawaii3.
Yes, it looks like _ttconv.cpp is the culprit here. Sloppy reference
handling (and I say that as the author of that file...) I've committed
some changes to SVN that seem to remove the leaks with
memleak_hawaii3.py and the PDF and PS backends.
Cheers,
Mike
Michael Droettboom wrote:
> I'm just
On Thu, Jul 31, 2008 at 10:05 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> No, you didn't screw up. It's just hard to arrive home to a pile of 1000's
> of e-mails... ;)
well, you are pressing through them with a remarkable terminator like
efficiency.
welcome back :-)
JDH
---
No, you didn't screw up. It's just hard to arrive home to a pile of
1000's of e-mails... ;)
Cheers,
Mike
John Hunter wrote:
> On Thu, Jul 31, 2008 at 9:33 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotli
Aha -- here from John (in another thread) is why those lines were
commented out:
On Sun, Jul 27, 2008 at 4:24 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> >if midPoint:
> >if self.gridOn:
> >self.gridline.draw(renderer)
> >if self.tick1On:
>
John Hunter wrote:
> On Sat, Jul 26, 2008 at 6:26 PM, John Hunter <[EMAIL PROTECTED]> wrote:
>
>
>>> stix_fonts_demo: error
>>>UnicodeDecodeError: 'rawunicodeescape' codec can't decode
>>>bytes in position 39-0: \U out of range
>>>
>
> I'm pretty sure this is the result o
On Thu, Jul 31, 2008 at 9:33 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/transforms.py",
>>> line 1072, in transform_point
>>> assert len(point) == self.input_dims
>>>
>
> I can't reproduce this here
I'm just getting back from vacation and will add this to my TODO list.
I have some thoughts...
Cheers,
Mike
Eric Firing wrote:
> 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 illustr
John Hunter wrote:
>> symlog_demo: rendering causes the following error
>>File
>> "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib/transforms.py",
>> line 1072, in transform_point
>> assert len(point) == self.input_dims
>>
I can't reproduce t
Paul Kienzle wrote:
> 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()
John Hunter wrote:
> I'm not too keen on having general math in one module and matlab
> compatible math in another, in part because this will be confusing to
> folks not too familiar with matlab, and as time passes (I never use it
> anymore) that is starting to include me. I think we could avoid s
There was a thread on this a few weeks ago (which unfortunately I can't
find). Supporting wx 2.6 is not a goal for the Wx backend in 0.98.x.
It is impossible to support matplotlib's new drawing API (which includes
Bezier curves and alpha transparency) with the old wx API. If you need
to use
What's happening here is that the Hammer projection uses interpolation
to make the lines follow the curve of the projection. Obviously with
markers, we don't want that interpolation. The fix is to just use
transform_points rather than transform_path with markers. This is now
fixed in SVN r59
Arrays are not supported with the built-in math engine. You'll need to
set math.usetex to True.
Cheers,
Mike
Nils Wagner wrote:
> 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]$')
(Just back from vacation)
That change was long enough ago that I don't remember the reason -- it
may have just been a debugging hack that made its way into the code.
Let's leave it uncommented until someone notices breakage... ;)
Cheers,
Mike
Ryan May wrote:
> Eric Firing wrote:
>
>>> Anyon
(Sorry for the delay, just back from vacation).
I don't have access to that version of gcc on Solaris to test. However,
if you find a preprocessor workaround that works for you, I'm happy to
test it on Linux/Mac/Windows and commit.
Cheers,
Mike
Peter C. Norton wrote:
> On solaris with gcc-4.3.
16 matches
Mail list logo