On Thursday 24 April 2008 10:45:33 pm John Hunter wrote:
> On Thu, Apr 24, 2008 at 9:23 PM, Darren Dale <[EMAIL PROTECTED]>
wrote:
> > I have been developing a data acquisition and analysis program for my
> > lab, and we are actually in the process of using it it this week and next
> > to run exp
On Thu, Apr 24, 2008 at 9:23 PM, Darren Dale <[EMAIL PROTECTED]> wrote:
> I have been developing a data acquisition and analysis program for my lab,
> and
> we are actually in the process of using it it this week and next to run
> experiments with our visiting scientists. I've been running mat
On Thursday 24 April 2008 09:48:18 pm John Hunter wrote:
> On Thu, Apr 24, 2008 at 5:03 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> > Darren,
> >
> > It is open for discussion. Here are some factors:
> >
> > 1) In my experience, numpy is easy to build from source--easier than
> > matplotlib.
>
On Thu, Apr 24, 2008 at 5:03 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> Darren,
>
> It is open for discussion. Here are some factors:
>
> 1) In my experience, numpy is easy to build from source--easier than
> matplotlib.
This is my view too -- if you rely on or can build svn mpl, I seen no
r
Darren Dale wrote:
> On Thursday 24 April 2008 03:09:43 pm John Hunter wrote:
>> On Thu, Apr 24, 2008 at 1:32 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>>> Darren,
>>>
>>> In an earlier thread on matplotlib-users, when this first came up, John
>>> noted that numpy svn should be required for pre
Hum, a quite common discussion (we have had it at the nipy sprint, for
instance). My feeling is that you want to avoid depending on SVN
versions, unless there is a huge gain. The reason is that you loose
tester and potential contributors. In addition it makes it harder to get
the whole stack in a c
On Thursday 24 April 2008 03:09:43 pm John Hunter wrote:
> On Thu, Apr 24, 2008 at 1:32 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> > Darren,
> >
> > In an earlier thread on matplotlib-users, when this first came up, John
> > noted that numpy svn should be required for present mpl svn, so
> >
On Thu, Apr 24, 2008 at 3:32 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> Agreed. If there were a meta-class usage that was crystal-clear after a
> little inspection, and that actually made the code easier to understand and
> maintain, I would consider it.
>
> I know that when we talked in Kona
John Hunter wrote:
> On Thu, Apr 24, 2008 at 2:21 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> On a related note, what about python >= 2.4 instead of 2.3? This is not
>> something I have a strong opinion about, but I think it might also be a
>> reasonable time to let 2.4 be the minimum requir
On Thu, Apr 24, 2008 at 2:21 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> On a related note, what about python >= 2.4 instead of 2.3? This is not
> something I have a strong opinion about, but I think it might also be a
> reasonable time to let 2.4 be the minimum requirement.
I think python 2.4
On Thu, Apr 24, 2008 at 2:21 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> On a related note, what about python >= 2.4 instead of 2.3? This is not
> something I have a strong opinion about, but I think it might also be a
> reasonable time to let 2.4 be the minimum requirement.
As a point of ref
John Hunter wrote:
> On Thu, Apr 24, 2008 at 1:32 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>> Darren,
>>
>> In an earlier thread on matplotlib-users, when this first came up, John
>> noted that numpy svn should be required for present mpl svn, so
>> instead of fixing the attempted workaround
On Thu, Apr 24, 2008 at 1:32 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> Darren,
>
> In an earlier thread on matplotlib-users, when this first came up, John
> noted that numpy svn should be required for present mpl svn, so
> instead of fixing the attempted workaround for 1.04 I took it out and
Darren,
In an earlier thread on matplotlib-users, when this first came up, John
noted that numpy svn should be required for present mpl svn, so
instead of fixing the attempted workaround for 1.04 I took it out and
instead put a numpy version check in matplotlib.__init__.
Eric
Darren Dale wr
Mike,
One of your cleanups might have introduced a problem?
Eric
Updated to revision 5071.
[EMAIL PROTECTED]:~/programs/py/mpl/mpl_trunk$ psb
BUILDING MATPLOTLIB
matplotlib: 0.98pre
python: 2
It looks like the recent modification to transforms.py to update datalims only
when valid data are available is broken for numpy-1.04. In
tranforms.Bbox.update_from_data_xy, with numpy-1.04, the following line:
xym = ma.masked_where(~npy.isfinite(xy), xy)
fails with:
File "/usr/lib64/python2
Paul Kienzle wrote:
> Hi,
>
> The superscripts in mpl don't seem to be placed at the correct height for
> small fonts. The y-tics on the attached plot shows this. The effect is
> similar in svg and pdf backends.
>
Thanks. When looking up the x-height, the code was not taking the font
size in
17 matches
Mail list logo
