John Hunter wrote:
> On Mon, Aug 3, 2009 at 2:40 PM, Eric Firing wrote:
>> John Hunter wrote:
>>> On Mon, Aug 3, 2009 at 2:15 PM, John Hunter wrote:
>>>
This may have been Eric's change to clean up the pylab imports -- all
the mlab imports come before the pylab imports. Was this intentio
Hi,
On 3 Aug 2009, at 17:39, Michael Droettboom wrote:
> Is there an additional step to install mathtex? I thought the goal
> was to make "python setup.py install" work out of the box.
This was the goal and I got quite close to achieving it. This latter
parts of this thread deal with the spe
John Hunter writes:
> On Wed, Jul 22, 2009 at 8:15 AM, Jouni K. Seppänen wrote:
>
>> I finally committed the "boilerplate" variant. It seems to pass the
>> tests in pylab_examples, but now might be a good time for everyone to
>> take a look to see if I have broken anything.
>
> There is one probl
In article
<88e473830908011043u47782cf3qa37376e3caa17...@mail.gmail.com>,
John Hunter wrote:
> I tried testing the OSX binaries I built Friday on my local OSX laptop
> today, and had a problem with the mkpg installer
>
> http://drop.io/xortel1/asset/matplotlib-0-99-0-rc1-py2-5-macosx10-5-zip
>
On Mon, Aug 3, 2009 at 2:40 PM, Eric Firing wrote:
> John Hunter wrote:
>>
>> On Mon, Aug 3, 2009 at 2:15 PM, John Hunter wrote:
>>
>>> This may have been Eric's change to clean up the pylab imports -- all
>>> the mlab imports come before the pylab imports. Was this intentional?
>>> My guess is n
John Hunter wrote:
> On Mon, Aug 3, 2009 at 2:15 PM, John Hunter wrote:
>
>> This may have been Eric's change to clean up the pylab imports -- all
>> the mlab imports come before the pylab imports. Was this intentional?
>> My guess is not, since np.loadtxt is the replacement for pylab.load.
>> I
On Mon, Aug 3, 2009 at 2:15 PM, John Hunter wrote:
> This may have been Eric's change to clean up the pylab imports -- all
> the mlab imports come before the pylab imports. Was this intentional?
> My guess is not, since np.loadtxt is the replacement for pylab.load.
> I prefer to do what we are c
I just noticed pylab.load now points to np.load when it used to point
to mlab.load
In [17]: import pylab
In [18]: import numpy
In [19]: pylab.load is numpy.load
Out[19]: True
This may have been Eric's change to clean up the pylab imports -- all
the mlab imports come before the pylab imports. W
I just did a clean install into a new virtualenv and I get the following
when running mathtext_demo.py:
/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/backends/backend_agg.py:165:
UserWarning: matplotlib was compiled without mathtex support. Math will
not be rendered.
'Math will not
On 2009-08-02 00:18, Michiel de Hoon wrote:
>> Is one of these two locations preferable for the
>> default?
>
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/
>
> is preferable.
>
> The location depends on whether the user has a framework Python or a normal
> static
Hi all,
I have just finished going over the mathtex branch and it appears to
be totally feature complete. Furthermore, by using the newest version
of mathtex it also benefits from the recent rendering improvements.
I am therefore interested to hear peoples comments on it/what can be
improve
Hello,
I'm working on a pyglet backend for matplotlib and I have a few
questions. Currently the renderer is a subclass of the Agg renderer and
it seems to be working properly. I intended only to re-implement the
'draw_image' method to benefit from fast image display using
OpenGL/texture/shader.
12 matches
Mail list logo
