[Numpy-discussion] NumPy 1.11.0b3 released.

Post by Charles R Harris
I'm pleased to announce the release of NumPy 1.11.0b3. This beta contains

[clip]

Post by Charles R Harris
Please test, hopefully this will be that last beta needed.

FWIW, https://travis-ci.org/pv/testrig/builds/108384173

Charles R Harris

2016-02-10 22:36:09 UTC

Post by Pauli Virtanen

Post by Charles R Harris
I'm pleased to announce the release of NumPy 1.11.0b3. This beta contains

[clip]

Post by Charles R Harris
Please test, hopefully this will be that last beta needed.

FWIW, https://travis-ci.org/pv/testrig/builds/108384173

Thanks Pauli, very interesting.

Chuck

j***@gmail.com

2016-02-10 23:55:09 UTC

Post by Charles R Harris
I'm pleased to announce the release of NumPy 1.11.0b3. This beta

contains
[clip]

Post by Charles R Harris
Please test, hopefully this will be that last beta needed.

FWIW, https://travis-ci.org/pv/testrig/builds/108384173

Thanks Pauli, very interesting.

Thanks Pauli, me too

is this intended?:

return np.r_[[np.nan] * head, x, [np.nan] * tail]
TypeError: 'numpy.float64' object cannot be interpreted as an index

In the old times of Python 2.x, statsmodels avoided integers so we don't
get accidental integer division.
Python wanted float() everywhere. Looks like numpy wants int() everywhere.
(fixed in statsmodels master)

Josef

Post by Charles R Harris
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Andreas Mueller

2016-02-12 21:17:30 UTC

Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.

Thanks,
Andy

Post by Charles R Harris
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue
that remains to be decided is whether or not to postpone raising an
error for floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test,
hopefully this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for
me, but there are still variations to try. The wheeluploader
downloaded wheels as it should, but could not upload them, giving the
error message "HTTPError: 413 Client Error: Request Entity Too Large
for url: https://www.python.org/pypi". Firefox also complains that
http://wheels.scipy.org is incorrectly configured with an invalid
certificate.
Enjoy,
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Nathan Goldbaum

2016-02-12 21:19:56 UTC

https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos without
hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta contains
additional bug fixes as well as limiting the number of FutureWarnings
raised by assignment to masked array slices. One issue that remains to be
decided is whether or not to postpone raising an error for floats used as
indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and both
sources and OS X wheels are availble on pypi. Please test, hopefully this
will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for me,
but there are still variations to try. The wheeluploader downloaded wheels
as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox also
complains that http://wheels.scipy.org is incorrectly configured with an
invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

j***@gmail.com

2016-02-16 03:50:44 UTC

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and both
sources and OS X wheels are availble on pypi. Please test, hopefully this
will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for
me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox also
complains that http://wheels.scipy.org is incorrectly configured with
an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up in
examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to an
index
the actual code uses pop on a python list with a return from
np.where(...)[0] that returns a one element int64 array
Josef

Charles R Harris

2016-02-16 04:05:54 UTC

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test, hopefully
this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for
me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox
also complains that http://wheels.scipy.org is incorrectly configured
with an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up in
examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to an
index

Looks like a misleading error message. Apparently it requires scalar arrays
(ndim == 0)

In [3]: list(range(5))[np.array(0)]
Out[3]: 0

Chuck

j***@gmail.com

2016-02-16 04:15:49 UTC

On Mon, Feb 15, 2016 at 11:05 PM, Charles R Harris <

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test, hopefully
this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for
me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox
also complains that http://wheels.scipy.org is incorrectly configured
with an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up in
examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to an
index

Looks like a misleading error message. Apparently it requires scalar
arrays (ndim == 0)
In [3]: list(range(5))[np.array(0)]
Out[3]: 0

We have a newer version of essentially same function a second time that
uses squeeze and that seems to work fine.

Just to understand

Why does this depend on the numpy version? I would have understood that
this always failed, but this code worked for several years.
https://github.com/statsmodels/statsmodels/issues/2817

Josef

Post by Charles R Harris
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Charles R Harris

2016-02-16 04:31:39 UTC

Post by j***@gmail.com
On Mon, Feb 15, 2016 at 11:05 PM, Charles R Harris <

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test, hopefully
this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail for
me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox
also complains that http://wheels.scipy.org is incorrectly
configured with an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up in
examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to an
index

Looks like a misleading error message. Apparently it requires scalar
arrays (ndim == 0)
In [3]: list(range(5))[np.array(0)]
Out[3]: 0

We have a newer version of essentially same function a second time that
uses squeeze and that seems to work fine.
Just to understand
Why does this depend on the numpy version? I would have understood that
this always failed, but this code worked for several years.
https://github.com/statsmodels/statsmodels/issues/2817

It's part of the indexing cleanup.

In [2]: list(range(5))[np.array([0])]
/home/charris/.local/bin/ipython:1: VisibleDeprecationWarning: converting
an array with ndim > 0 to an index will result in an error in the future
#!/usr/bin/python
Out[2]: 0

The use of multidimensional arrays as indexes is likely a coding error. Or
so we hope...

Chuck

j***@gmail.com

2016-02-16 05:09:25 UTC

On Mon, Feb 15, 2016 at 11:31 PM, Charles R Harris <

Post by j***@gmail.com
On Mon, Feb 15, 2016 at 11:05 PM, Charles R Harris <

On Fri, Feb 12, 2016 at 4:19 PM, Nathan Goldbaum <

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test, hopefully
this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail
for me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox
also complains that http://wheels.scipy.org is incorrectly
configured with an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up in
examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to an
index

Looks like a misleading error message. Apparently it requires scalar
arrays (ndim == 0)
In [3]: list(range(5))[np.array(0)]
Out[3]: 0

We have a newer version of essentially same function a second time that
uses squeeze and that seems to work fine.
Just to understand
Why does this depend on the numpy version? I would have understood that
this always failed, but this code worked for several years.
https://github.com/statsmodels/statsmodels/issues/2817

It's part of the indexing cleanup.
In [2]: list(range(5))[np.array([0])]
/home/charris/.local/bin/ipython:1: VisibleDeprecationWarning: converting
an array with ndim > 0 to an index will result in an error in the future
#!/usr/bin/python
Out[2]: 0
The use of multidimensional arrays as indexes is likely a coding error. Or
so we hope...

Thanks for the explanation

Or, it forces everyone to watch out for the color of the ducks :)

It's just a number, whether it's python scalar, numpy scalar, 1D or 2D.
And once we squeeze, we cannot iterate over it anymore.

This looks like the last problem with have in statsmodels master.
Part of the reason that 0.10 hurt quite a bit is that we are using in
statsmodels some of the grey zones so we don't have to commit to a specific
usage. Even if a user or developer tries a "weird" case, it works for most
of the results, but breaks in some unknown places.

(In the current case a cryptic exception would be raised if the user has
two constant columns in the regression. Which is fine for some usecases but
not for every result.)

Josef

Post by Charles R Harris
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

j***@gmail.com

2016-02-16 05:13:28 UTC

Post by j***@gmail.com
On Mon, Feb 15, 2016 at 11:31 PM, Charles R Harris <

Post by j***@gmail.com
On Mon, Feb 15, 2016 at 11:05 PM, Charles R Harris <

On Fri, Feb 12, 2016 at 4:19 PM, Nathan Goldbaum <

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Post by Andreas Mueller
Hi.
Where can I find the changelog?
It would be good for us to know which changes are done one purpos
without hunting through the issue tracker.
Thanks,
Andy
Hi All,
I'm pleased to announce the release of NumPy 1.11.0b3. This beta
contains additional bug fixes as well as limiting the number of
FutureWarnings raised by assignment to masked array slices. One issue that
remains to be decided is whether or not to postpone raising an error for
floats used as indexes. Sources may be found on Sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.0b3/> and
both sources and OS X wheels are availble on pypi. Please test, hopefully
this will be that last beta needed.
As a note on problems encountered, twine uploads continue to fail
for me, but there are still variations to try. The wheeluploader downloaded
wheels as it should, but could not upload them, giving the error message
<https://www.python.org/pypi>https://www.python.org/pypi". Firefox
also complains that http://wheels.scipy.org is incorrectly
configured with an invalid certificate.
Enjoy,
Chuck
_______________________________________________
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

(try to send again)

another indexing question: (not covered by unit test but showed up
in examples in statsmodels)
This works in numpy at least 1.9.2 and 1.6.1 (python 2.7, and python 3.4)

list(range(5))[np.array([0])]

0
on numpy 0.11.0b2 (I'm not yet at b3) (python 3.4)
I get the same exception as here but even if there is just one element

list(range(5))[np.array([0, 1])]

File "<pyshell#7>", line 1, in <module>
list(range(5))[np.array([0, 1])]
TypeError: only integer arrays with one element can be converted to
an index

Looks like a misleading error message. Apparently it requires scalar
arrays (ndim == 0)
In [3]: list(range(5))[np.array(0)]
Out[3]: 0

We have a newer version of essentially same function a second time that
uses squeeze and that seems to work fine.
Just to understand
Why does this depend on the numpy version? I would have understood that
this always failed, but this code worked for several years.
https://github.com/statsmodels/statsmodels/issues/2817

It's part of the indexing cleanup.
In [2]: list(range(5))[np.array([0])]
/home/charris/.local/bin/ipython:1: VisibleDeprecationWarning: converting
an array with ndim > 0 to an index will result in an error in the future
#!/usr/bin/python
Out[2]: 0
The use of multidimensional arrays as indexes is likely a coding error.
Or so we hope...

Thanks for the explanation
Or, it forces everyone to watch out for the color of the ducks :)
It's just a number, whether it's python scalar, numpy scalar, 1D or 2D.
And once we squeeze, we cannot iterate over it anymore.
This looks like the last problem with have in statsmodels master.
Part of the reason that 0.10 hurt quite a bit is that we are using in
statsmodels some of the grey zones so we don't have to commit to a specific
usage. Even if a user or developer tries a "weird" case, it works for most
of the results, but breaks in some unknown places.

I meant 1.11 here.

Post by j***@gmail.com
(In the current case a cryptic exception would be raised if the user has
two constant columns in the regression. Which is fine for some usecases but
not for every result.)
Josef

Post by Charles R Harris
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Sebastian Berg

2016-02-16 12:05:31 UTC

<skip>

Post by j***@gmail.com
Or, it forces everyone to watch out for the color of the ducks :)
It's just a number, whether it's python scalar, numpy scalar, 1D or 2D.
And once we squeeze, we cannot iterate over it anymore.
This looks like the last problem with have in statsmodels master.
Part of the reason that 0.10 hurt quite a bit is that we are using
in statsmodels some of the grey zones so we don't have to commit to
a specific usage. Even if a user or developer tries a "weird" case,
it works for most of the results, but breaks in some unknown
places.

I meant 1.11 here.

The reason for this part is that `arr[np.array([1])]` is very different
from `arr[np.array(1)]`. For `list[np.array([1])]` if you allow
`operator.index(np.array([1]))` you will not get equivalent results for
lists and arrays.

The normal array result cannot work for lists. We had open bug reports
about it. Of course I dislike it in any case ;), but that is the
reasoning behind being a bit more restrictive for `__index__`.

- Sebastian

Post by j***@gmail.com
(In the current case a cryptic exception would be raised if the
user has two constant columns in the regression. Which is fine for
some usecases but not for every result.)
Josef

Post by Charles R Harris
Chuck
_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Andreas Mueller

2016-02-17 16:12:39 UTC

Post by Nathan Goldbaum
https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst

Thanks.
That doesn't cover the backward incompatible change to
assert_almost_equal and assert_array_almost_equal,
right?

Charles R Harris

2016-02-17 17:07:55 UTC