Michael Droettboom wrote:
> Well, if it's any consolation -- I just finished setting up the
> maintenance branch for 0.98.5, so there's a place for this fix to go... ;)
>
Okay, I just applied a patch to the 0.98.5 maintenance branch. Checked
it with numpy 1.2.1 and 1.3.0.dev6139. Both work fine.
Well, if it's any consolation -- I just finished setting up the
maintenance branch for 0.98.5, so there's a place for this fix to go... ;)
Mike
Manuel Metz wrote:
> Manuel Metz wrote:
>
>> Jae-Joon Lee wrote:
>>
>>> I just committed the change. Although the change is trivial, I didn't
>>
Manuel Metz wrote:
> Jae-Joon Lee wrote:
>> I just committed the change. Although the change is trivial, I didn't
>> tested it in the numpy 1.2 or the svn version.
>
> Aaaargh, with numpy 1.2.1 this produces a warning !!! Very unlucky,
> since 0.98.5 is released...
See here: http://projects.scipy
Jae-Joon Lee wrote:
> I just committed the change. Although the change is trivial, I didn't
> tested it in the numpy 1.2 or the svn version.
Aaaargh, with numpy 1.2.1 this produces a warning !!! Very unlucky,
since 0.98.5 is released...
> -JJ
>
>
> On Sun, Dec 7, 2008 at 3:24 PM, John Hunter
John Hunter <[EMAIL PROTECTED]> writes:
> I think the version check is a good idea, so people won't get the
> annoying warning. Could you add this?
>
> Sent from my iPhone
>
> On Dec 7, 2008, at 2:22 PM, "Jae-Joon Lee" <[EMAIL PROTECTED]> wrote:
>
> > I'm currently using numpy 1.1.1 and np.h
On Sun, Dec 7, 2008 at 2:55 PM, Jae-Joon Lee <[EMAIL PROTECTED]> wrote:
> I just committed the change. Although the change is trivial, I didn't
> tested it in the numpy 1.2 or the svn version.
I tested on numpy svn on a couple of platforms (OS X and linux) and
this looks OK from my end.
-
I just committed the change. Although the change is trivial, I didn't
tested it in the numpy 1.2 or the svn version.
-JJ
On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> I think the version check is a good idea, so people won't get the annoying
> warning. Could you add t
I think the version check is a good idea, so people won't get the
annoying warning. Could you add this?
Sent from my iPhone
On Dec 7, 2008, at 2:22 PM, "Jae-Joon Lee" <[EMAIL PROTECTED]> wrote:
> I'm currently using numpy 1.1.1 and np.histogram behave differently
> depending on the "new" valu
I'm currently using numpy 1.1.1 and np.histogram behave differently
depending on the "new" value.
ubuntu interpid and debian sid has numpy 1.1.1.1 and I presume that
this different behavior is still there.
So, as far as we're going to support numpy 1.1 and later, we may
better not to drop the "new"
Axes.hist calls np.histogram with the "new" kwarg, which triggers a
deprecation warning with svn numpy. Anyone have an opinion on whether
this kwarg should be included in the upcoming mpl release?
JDH
--
SF.Net email is
10 matches
Mail list logo
