Hello,
thanks for you feedback.
Sorry, if thie question is stupid and the case below does not make
sense.
I am just trying to understand the logic.
For
x = np.random.rand(2,3)
x[True]
x[(True,)]
or
x[False]
x[(False,)]
where True and False are not arrays,
it will pick the first or second r
It sounds like you're using an old version of numpy, where boolean scalars
were interpreted as integers.
What version are you using?
Eric
On Thu, Dec 14, 2017, 04:27 Joe wrote:
> Hello,
> thanks for you feedback.
>
> Sorry, if thie question is stupid and the case below does not make
> sense.
>
Thanks Chuck!
And a huge thanks to that awesome list of contributors!!!
-Chris
Sent from my iPhone
On Dec 13, 2017, at 2:55 PM, Charles R Harris
wrote:
Hi All,
On behalf of the NumPy team, I am pleased to announce NumPy 1.14.0rc1. Numpy
1.14.0rc1 is the result of seven months of work and con
On Thu, 2017-12-14 at 16:24 +, Eric Wieser wrote:
> It sounds like you're using an old version of numpy, where boolean
> scalars were interpreted as integers.
> What version are you using?
> Eric
>
Indeed, you are maybe using a pre 1.9 version (post 1.9 should at least
have a DeprecationWarni
Hi,
you are right. I am using two different versions, Numpy 1.10.4 and 1.9.0
Both show this behavior.
Numpy 1.11.1 also does, but now raises VisibleDeprecationWarning:
using a boolean instead of an integer will result in an error in the
future
Thanks!
Am 14.12.2017 21:37 schrieb Sebastian
