Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Jouni K . Seppänen
John Hunter writes: > I confirmed this on linux and added an issue on github: > https://github.com/matplotlib/matplotlib/issues/478. Pull request #479 fixes the immediate problem, but for the long term we should fix the handling of redirection in get_sample_data. -- Jouni K. Seppänen http://

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Eric Firing
On 09/18/2011 11:15 AM, John Hunter wrote: > On Sun, Sep 18, 2011 at 4:02 PM, Eric Firing wrote: >> There is a way to deal with this now: define our own copyto which uses >> np.copyto if it exists, and falls back on putnav otherwise. I think this >> can be done with reasonable safety and no loss

Re: [matplotlib-devel] Quantization of normalized float to uint8

2011-09-18 Thread Eric Firing
On 09/18/2011 09:30 AM, Christoph Gohlke wrote: > Hello, > > matplotlib uses int(x*255) or np.array(x*255, np.uint8) to quantize > normalized floating point numbers x in the range [0.0 to 1.0] to > integers in the range [0 to 255]. This way only 1.0 is mapped to 255, > not for example 0.999. Is thi

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Fernando Perez
On Sun, Sep 18, 2011 at 2:02 PM, Eric Firing wrote: > There is a way to deal with this now: define our own copyto which uses > np.copyto if it exists, and falls back on putnav otherwise.  I think > this can be done with reasonable safety and no loss of performance.  The > only question is where to

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread John Hunter
On Sun, Sep 18, 2011 at 4:02 PM, Eric Firing wrote: > There is a way to deal with this now: define our own copyto which uses > np.copyto if it exists, and falls back on putnav otherwise.  I think this > can be done with reasonable safety and no loss of performance.  The only > question is where to

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Eric Firing
On 09/18/2011 09:46 AM, Fernando Perez wrote: > On Sun, Sep 18, 2011 at 12:41 PM, John Hunter wrote: >> >> I'm on 11.04, 64 bit also. >> >> What does this give you? >> >> > ython -c 'import numpy as np; print np.__version__; x = >> np.random.rand(10); np.putmask(x, x<0.5, 0.)' >> >> I only get

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Eric Firing
On 09/18/2011 09:54 AM, John Hunter wrote: >> putmask was deprecated in favor of copyto only 2 months ago; copyto >> didn't even exist before that. So we certainly can't replace putmask >> with copyto in mpl. >> >> http://currents.soest.hawaii.edu/hgstage/numpy_from_git/rev/26533521322b > > > The p

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Eric Firing
On 09/18/2011 09:54 AM, John Hunter wrote: >> putmask was deprecated in favor of copyto only 2 months ago; copyto >> didn't even exist before that. So we certainly can't replace putmask >> with copyto in mpl. >> >> http://currents.soest.hawaii.edu/hgstage/numpy_from_git/rev/26533521322b > > > The p

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread John Hunter
> putmask was deprecated in favor of copyto only 2 months ago; copyto > didn't even exist before that. So we certainly can't replace putmask > with copyto in mpl. > > http://currents.soest.hawaii.edu/hgstage/numpy_from_git/rev/26533521322b The putmasks in colors.py are simple and could be replace

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Fernando Perez
On Sun, Sep 18, 2011 at 12:41 PM, John Hunter wrote: > > I'm on 11.04, 64 bit also. > > What does this give you? > >  > ython -c 'import numpy as np; print np.__version__; x = > np.random.rand(10); np.putmask(x, x<0.5, 0.)' > > I only get the version string 2.0.0.dev-aded70c, no warning. It seems

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Eric Firing
On 09/18/2011 09:24 AM, Fernando Perez wrote: > On Sun, Sep 18, 2011 at 12:05 PM, John Hunter wrote: >> I can fix these putmask calls, but strangely I am not seeing the >> deprecation warning on numpy and mpl HEAD putmask was deprecated in favor of copyto only 2 months ago; copyto didn't even ex

[matplotlib-devel] Quantization of normalized float to uint8

2011-09-18 Thread Christoph Gohlke
Hello, matplotlib uses int(x*255) or np.array(x*255, np.uint8) to quantize normalized floating point numbers x in the range [0.0 to 1.0] to integers in the range [0 to 255]. This way only 1.0 is mapped to 255, not for example 0.999. Is this really intended or would not the largest floating poi

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Fernando Perez
On Sun, Sep 18, 2011 at 12:05 PM, John Hunter wrote: > I can fix these putmask calls, but strangely I am not seeing the > deprecation warning on numpy and mpl HEAD > >  In [1]: print np.__version__ >  2.0.0.dev-aded70c > >  In [2]: print matplotlib.__version__ >  1.1.0 > >  In [3]: imshow(rand(10,

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread John Hunter
On Sun, Sep 18, 2011 at 1:17 AM, Christoph Gohlke wrote: > The master branch builds OK on Windows and so far almost everything > worked well. > > I have trouble receiving the sample_data from github via cbook.py. There > are frequent HTTP 304 (Not Modified) and 500 (Internal Server Error) > excep

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread John Hunter
On Sun, Sep 18, 2011 at 1:44 PM, Fernando Perez wrote: > I'm not sure why, but as of a few weeks ago, with recent builds of > numpy/mpl I always get these warnings: > > In [1]: imshow(rand(10,10)) > Out[1]: > > In [2]: > /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/colors.py:519:

Re: [matplotlib-devel] release: stalled again?

2011-09-18 Thread Fernando Perez
I'm not sure why, but as of a few weeks ago, with recent builds of numpy/mpl I always get these warnings: In [1]: imshow(rand(10,10)) Out[1]: In [2]: /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/colors.py:519: DeprecationWarning: putmask has been deprecated. Use copyto with 'wher

[matplotlib-devel] [Basemap] Add missing shebang in scripts in data/ dir

2011-09-18 Thread Sandro Tosi
Hello, there are some scripts in the data/ dir (I'm not even sure they're needed at all, but they are there) missing the shebang; attached patch adds it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/Sa

Re: [matplotlib-devel] [Basemap] Please explicit mention copyright and license

2011-09-18 Thread Sandro Tosi
On Sun, Sep 18, 2011 at 16:53, John Hunter wrote: > Take a look at > > https://github.com/matplotlib/basemap/blob/master/README > > Does this have everything you need? Gaah, I was overwhelmed by the third-party tools copyright/licenses I missed the basemap ones: thanks John! -- Sandro Tosi (aka

Re: [matplotlib-devel] [Basemap] Please explicit mention copyright and license

2011-09-18 Thread John Hunter
On Sun, Sep 18, 2011 at 9:46 AM, Sandro Tosi wrote: > Hello, > I'm packaging basemap for Debian, but as you know, we always have some > problems :) > > One important part of Debian packaging is the license/copyright > checks, but for basemap I can't find any explicit indication of them: > > for li

[matplotlib-devel] [Basemap] Don't recompile nad2bin when running setup.py clean

2011-09-18 Thread Sandro Tosi
Hi, when running python setup.py clean nad2bin is compiled. I've just worked around with the attached patch, so it would be nice if you can integrate it upstream or come up with a better solution. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.alterv

[matplotlib-devel] [Basemap] Please explicit mention copyright and license

2011-09-18 Thread Sandro Tosi
Hello, I'm packaging basemap for Debian, but as you know, we always have some problems :) One important part of Debian packaging is the license/copyright checks, but for basemap I can't find any explicit indication of them: for license I have OSI Approved that doesn't mean anything (legally

Re: [matplotlib-devel] 3 test failures

2011-09-18 Thread Jouni K . Seppänen
Eric Firing writes: > image_interp pdf I bisected this to 79ca159 recover old behavior for 'nearest' interpolation and introduces 'none'. close #83 which changes the meaning of "nearest" interpolation but does not change the corresponding test. I'll send a pull request to fix this soon. This