using new in axes.hist

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

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

···

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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" <lee.j.joon@...149...> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 <jdh2358@...149...> wrote:

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" <lee.j.joon@...149...> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

I tested on numpy svn on a couple of platforms (OS X and linux) and
this looks OK from my end.

···

On Sun, Dec 7, 2008 at 2:55 PM, Jae-Joon Lee <lee.j.joon@...149...> 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.

John Hunter <jdh2358@...149...> 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

> 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" silently.

Debian lenny (which is currently in freeze and will be the next
stable) has numpy 1.1 at present.

It is possible that the package maintainers will try to get a later
version in - but you should check before relying on it.

Chris

···

On Dec 7, 2008, at 2:22 PM, "Jae-Joon Lee" <lee.j.joon@...149...> 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...

···

-JJ

On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <jdh2358@...149...> wrote:

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" <lee.j.joon@...149...> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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.org/scipy/numpy/ticket/797

"08/05/08 10:47:34 changed by dhuard

  For version 1.2, I set new=None by default, which triggers the new
  semantics and prints a warning. Setting new to True will trigger the
  new semantics but won't print a warning. Done in r5611."

···

-JJ

On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <jdh2358@...149...> wrote:

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" <lee.j.joon@...149...> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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... :wink:

Mike

Manuel Metz wrote:

···

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.org/scipy/numpy/ticket/797

"08/05/08 10:47:34 changed by dhuard

  For version 1.2, I set new=None by default, which triggers the new
  semantics and prints a warning. Setting new to True will trigger the
  new semantics but won't print a warning. Done in r5611."

-JJ

On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <jdh2358@...149...> wrote:
      

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" <lee.j.joon@...149...> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> wrote:
          

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
      
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
    
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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... :wink:

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.

mm

···

Manuel Metz wrote:

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.org/scipy/numpy/ticket/797

"08/05/08 10:47:34 changed by dhuard

  For version 1.2, I set new=None by default, which triggers the new
  semantics and prints a warning. Setting new to True will trigger the
  new semantics but won't print a warning. Done in r5611."

-JJ

On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <jdh2358@...149...> wrote:
     

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" <lee.j.joon@...149...> >>>>> wrote:

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" silently.
We may check the version number of the numpy in the hist() function,
and call np.histogram() accordingly.

-JJ

On Sat, Dec 6, 2008 at 4:33 PM, John Hunter <jdh2358@...149...> >>>>>> wrote:
         

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 Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09
to help
pave the way to the Next Web now. Learn more and register at

http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

------------------------------------------------------------------------------

SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to
help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
      
------------------------------------------------------------------------------

SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to
help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
    
------------------------------------------------------------------------------

SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel