On Tue, Mar 26, 2013 at 6:32 PM, Ondřej Čertík wrote:
[...]
> Yes. I created an issue here for them to test it:
>
> https://github.com/scikit-learn/scikit-learn/issues/1809
>
> Just to make sure.
There doesn't seem to be any more problems, so I am releasing 1.7.1 now.
Ondrej
Hi,
On Sat, Apr 6, 2013 at 1:35 PM, Ralf Gommers wrote:
>
>
>
> On Sat, Apr 6, 2013 at 7:22 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sat, Apr 6, 2013 at 1:51 AM, Ralf Gommers
>> wrote:
>> >
>> >
>> >
>> > On Sat, Apr 6, 2013 at 4:47 AM, Matthew Brett
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >
Hi,
Not a developer here, but I was under the impression that you can only use
the BLAS/LAPACK libraries that where chosen at build time?
As a side note: I've read [1] that OpenBLAS on some systems could perform
quite well compared to ATLAS, I used some simple benchmarks [2] and noticed
that on m
On Sat, Apr 6, 2013 at 8:03 PM, Alex Ford wrote:
> Hello,
>
> Do any core developers or uses have guidance on how to resolve PR #3188
> (https://github.com/numpy/numpy/pull/3188) in relation to the pickling
> behavior of array scalar objects?
>
> To summarize, pickling array scalars with object fi
On Sat, Apr 6, 2013 at 7:22 PM, Matthew Brett wrote:
> Hi,
>
> On Sat, Apr 6, 2013 at 1:51 AM, Ralf Gommers
> wrote:
> >
> >
> >
> > On Sat, Apr 6, 2013 at 4:47 AM, Matthew Brett
> > wrote:
> >>
> >> Hi,
> >>
> >> On Fri, Apr 5, 2013 at 7:39 PM, wrote:
> >> >
> >> > It's not *any* cost, this g
On Sat, Apr 6, 2013 at 8:16 PM, Paul Ivanov wrote:
> Hi Ralf,
>
> Ralf Gommers, on 2013-04-06 10:51, wrote:
> > P.P.S. expect an identical response from me to future proposals that
> > include backwards compatibility breaks of heavily used functions for
> > something that's not a functional enha
Hello,
Do any core developers or uses have guidance on how to resolve PR #3188 (
https://github.com/numpy/numpy/pull/3188) in relation to the pickling
behavior of array scalar objects?
To summarize, pickling array scalars with object fields, which are produced
when indexing record arrays with obj
Hi Ralf,
Ralf Gommers, on 2013-04-06 10:51, wrote:
> P.P.S. expect an identical response from me to future proposals that
> include backwards compatibility breaks of heavily used functions for
> something that's not a functional enhancement or bug fix. Such proposals
> are just not OK.
but it is
Hi,
On Sat, Apr 6, 2013 at 10:18 AM, matti picus wrote:
> as a lurker, may I say that this discussion seems to have become
> non-productive?
Well - the discussion is about two things - as so often the case on numpy.
The first is about the particular change.
The second is implicit, and keeps co
Hi,
On Sat, Apr 6, 2013 at 1:51 AM, Ralf Gommers wrote:
>
>
>
> On Sat, Apr 6, 2013 at 4:47 AM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Fri, Apr 5, 2013 at 7:39 PM, wrote:
>> >
>> > It's not *any* cost, this goes deep and wide, it's one of the basic
>> > concepts of numpy that you want to re
as a lurker, may I say that this discussion seems to have become
non-productive?
It seems all agree that docs needs improvement, perhaps a first step would
be to suggest doc improvements, and then the need for renaming may become
self-evident, or not.
aww darn, ruined my lurker status.
Matti Picu
On Wed, Mar 20, 2013 at 2:57 PM, Pierre Barbier de Reuille <
pierre.barbierdereui...@gmail.com> wrote:
> Hey,
>
> I am trying to use titles for the record arrays. In the documentation, it
> is specified that any column can set to "None". However, trying this fails
> on numpy 1.6.2 because in np.co
On Sat, Apr 6, 2013 at 4:47 AM, Matthew Brett wrote:
> Hi,
>
> On Fri, Apr 5, 2013 at 7:39 PM, wrote:
> >
> > It's not *any* cost, this goes deep and wide, it's one of the basic
> > concepts of numpy that you want to rename.
>
> The proposal I last made was to change the default name to 'layout'
13 matches
Mail list logo
