On Mon, Jul 21, 2008 at 1:06 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
>>
>> On Mon, Jul 21, 2008 at 7:51 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
>>
>>> 2) Can someone explain to me why is_string_like in the cbook doesn't
>>> just do isinstance(obj,str)? Is there anything
John Hunter wrote:
> On Mon, Jul 21, 2008 at 7:51 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
>
>> 2) Can someone explain to me why is_string_like in the cbook doesn't
>> just do isinstance(obj,str)? Is there anything "string like" that won't
>> be caught be this isinstance call?
>
> In [65]:
On Mon, Jul 21, 2008 at 10:17 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> Similar level of question: What is the policy on using scipy in
> matplotlib? I want to use linear interpolation, and
> simple_linear_interpolation in the cbook doesn't do what I want. I
> imagine that we are trying to a
Hi,
Similar level of question: What is the policy on using scipy in
matplotlib? I want to use linear interpolation, and
simple_linear_interpolation in the cbook doesn't do what I want. I
imagine that we are trying to avoid dependence on scipy.
Thanks,
David
On Mon, 2008-07-21 at 08:42 -0500,
On Mon, Jul 21, 2008 at 7:51 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> 2) Can someone explain to me why is_string_like in the cbook doesn't
> just do isinstance(obj,str)? Is there anything "string like" that won't
> be caught be this isinstance call?
In [65]: s = u'jdh'
In [66]: isinsta
Hi,
On Sun, 2008-07-20 at 08:09 -1000, Eric Firing wrote:
> It sounds like there is time to do it before the release without messing
> up the release. Just make sure the backend_drivers.py test suite still
> runs OK. If you can add tests (i.e., examples run by backend_drivers)
> that exercise
David M. Kaplan wrote:
> Hi,
>
> Sorry about the problems. The labeling code is somewhat difficult to
> understand and I was using label indices when I should have used level
> indices (or vice-versa). I have a fix, but want to test it more before
> committing. Let me know when is a good time t
Hi John & All
> The only short term pressure for a point release is coming from
> debian, because they are having some trouble with our last point
> release. Because debian is an important platform, I want to get a
> point release out that satisfies their problems ASAP, but not before
> we are re
Hi,
Sorry about the problems. The labeling code is somewhat difficult to
understand and I was using label indices when I should have used level
indices (or vice-versa). I have a fix, but want to test it more before
committing. Let me know when is a good time to do it so that I don't
mess up a r
On Sat, Jul 19, 2008 at 8:02 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> We might want to consider, however, whether such extensive changes
> should be made immediately *before* a "bugfix" release. I think John is
> trying to get one out. I am already a little nervous about other recent
> and i
David,
I am reverting your changes to contour.py; that is, I am taking it back
to 5689. The problem is that running contour_demo.py, below, fails.
Some index accounting somewhere is getting fouled up. I don't have time
to investigate.
When you have it straightened out you can put the changes
11 matches
Mail list logo
