https://github.com/numpy/numpy/issues/7545
On Wed, Apr 13, 2016 at 3:38 PM, Nathaniel Smith wrote:
> I can reproduce in self-compiled 1.9, so it's not a new bug.
>
> I think something's going wrong with NPY_SIGINT_ON / NPY_SIGINT_OFF,
> where our special sigint handler is getting left in place ev
I can reproduce in self-compiled 1.9, so it's not a new bug.
I think something's going wrong with NPY_SIGINT_ON / NPY_SIGINT_OFF,
where our special sigint handler is getting left in place even after
our code finishes running.
Skimming the code, my best guess is that this is due to a race
conditio
On 13 Apr 2016 21:48, "Matthew Brett" wrote:
>
> On Wed, Apr 13, 2016 at 1:29 PM, Oscar Benjamin
> wrote:
> > On 13 April 2016 at 20:15, Matthew Brett
wrote:
> >> Done. If y'all are on linux, and you have pip >= 8.11, you should
> >> now see this kind of thing:
> >
> > That's fantastic. Thanks
On Wed, Apr 13, 2016 at 1:15 PM, Matthew Brett
wrote:
> On Tue, Apr 12, 2016 at 7:15 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Sat, Apr 2, 2016 at 6:11 PM, Matthew Brett
> wrote:
> >> On Fri, Mar 25, 2016 at 6:39 AM, Peter Cock
> wrote:
> >>> On Fri, Mar 25, 2016 at 3:02 AM, Robert T. McGi
On Wed, Apr 13, 2016 at 2:48 PM, Nathaniel Smith wrote:
> On Apr 13, 2016 9:08 AM, "Robert Kern" wrote:
> >
> > On Wed, Apr 13, 2016 at 3:17 AM, Antony Lee
> wrote:
> > >
> > > This kind of issue (see also
> https://github.com/numpy/numpy/issues/3511) has become more annoying now
> that indexin
On Apr 13, 2016 9:08 AM, "Robert Kern" wrote:
>
> On Wed, Apr 13, 2016 at 3:17 AM, Antony Lee wrote:
> >
> > This kind of issue (see also https://github.com/numpy/numpy/issues/3511)
> > has become more annoying now that indexing requires integers (indexing with
> > a float raises a VisibleDepre
On Wed, Apr 13, 2016 at 1:29 PM, Oscar Benjamin
wrote:
> On 13 April 2016 at 20:15, Matthew Brett wrote:
>> Done. If y'all are on linux, and you have pip >= 8.11, you should
>> now see this kind of thing:
>
> That's fantastic. Thanks Matt!
>
> I just test installed this and ran numpy.test(). Al
On 13 April 2016 at 20:15, Matthew Brett wrote:
> Done. If y'all are on linux, and you have pip >= 8.11, you should
> now see this kind of thing:
That's fantastic. Thanks Matt!
I just test installed this and ran numpy.test(). All tests passed but
then I got a segfault at the end by (semi-accid
Woot! \o/
On Wed, Apr 13, 2016 at 12:15 PM, Matthew Brett
wrote:
> On Tue, Apr 12, 2016 at 7:15 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Sat, Apr 2, 2016 at 6:11 PM, Matthew Brett
> wrote:
> >> On Fri, Mar 25, 2016 at 6:39 AM, Peter Cock
> wrote:
> >>> On Fri, Mar 25, 2016 at 3:02 AM, Ro
\o/
Thank you very much Matthew. I will upload the scikit-learn wheels soon.
--
Olivier
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Apr 12, 2016 at 7:15 PM, Matthew Brett wrote:
> Hi,
>
> On Sat, Apr 2, 2016 at 6:11 PM, Matthew Brett wrote:
>> On Fri, Mar 25, 2016 at 6:39 AM, Peter Cock
>> wrote:
>>> On Fri, Mar 25, 2016 at 3:02 AM, Robert T. McGibbon
>>> wrote:
I suspect that many of the maintainers of major
On Wed, Apr 13, 2016 at 8:06 AM, wrote:
>
> The difference is that Python 3 has long ints, (and doesn't have to
> overflow, AFAICS)
>
This is a good point. But if your float is so big that rounding it to an
integer would overflow int64, rounding is already a no-op. I'm sure this
has been done
On Wed, Apr 13, 2016 at 3:17 AM, Antony Lee wrote:
>
> This kind of issue (see also https://github.com/numpy/numpy/issues/3511)
has become more annoying now that indexing requires integers (indexing with
a float raises a VisibleDeprecationWarning). The argument "dividing an
uint by an int may giv
On Wed, Apr 13, 2016 at 4:31 AM, Stephan Hoyer wrote:
> On Wed, Apr 13, 2016 at 12:42 AM, Antony Lee
> wrote:
>
>> (Note that I am suggesting to switch to the new behavior regardless of
>> the version of Python.)
>>
>
> I would lean towards making this change only for Python 3. This is
> arguabl
On Wed, Apr 13, 2016 at 12:42 AM, Antony Lee
wrote:
> (Note that I am suggesting to switch to the new behavior regardless of the
> version of Python.)
>
I would lean towards making this change only for Python 3. This is arguably
more consistent with Python than changing the behavior on Python 2.
https://github.com/numpy/numpy/issues/3511 proposed (nearly three years
ago) to return an integer when `builtins.round` (which calls the `__round__
dunder method, and thereafter called `round` (... not to be confused with
`np.round`)) is called with a single argument. Currently, `round` returns
a
16 matches
Mail list logo
