On Wed, Jul 1, 2015 at 10:32 AM, Sebastian Berg
wrote:
> On Mi, 2015-07-01 at 10:05 -0400, josef.p...@gmail.com wrote:
> > About the deprecation warning for using another type than integers, in
> > ones, reshape, indexing and so on:
> >
> >
> > Wouldn't it be nicer to accept floats that are equal
On Mi, 2015-07-01 at 10:05 -0400, josef.p...@gmail.com wrote:
> About the deprecation warning for using another type than integers, in
> ones, reshape, indexing and so on:
>
>
> Wouldn't it be nicer to accept floats that are equal to an integer?
>
Hmmm, the biggest point was that the old soluti
About the deprecation warning for using another type than integers, in
ones, reshape, indexing and so on:
Wouldn't it be nicer to accept floats that are equal to an integer?
for example
>>> 5.0 == 5
True
>>> np.ones(10 / 2)
array([ 1., 1., 1., 1., 1.])
>>> 10 / 2 == 5
True
or the python 2
Hello,
the project is already successfully completed, but I thought for the
completeness (and documentation) give myself an answer on what I did wrong and
what the correct solution was.
I. I didn’t realise that parameter ordering was crucial. Somehow I just had
forgotten this knowledge, but not
