> >
> > >From a practical standpoint, I believe that people implementing large
> > changes to the numpy codebase, or any other core scipy package, should
> > think really hard about their impact. I do realise that the changes are
> > discussed on the mailing lists, but there is a lot of activity to
On Fri, Sep 28, 2012 at 10:23 PM, Gael Varoquaux <
gael.varoqu...@normalesup.org> wrote:
> Hi numpy developers,
>
> First of all, thanks a lot for the hard work you put in numpy. I know
> very well that maintaining such a core library is a lot of effort and a
> service to the community. But "with g
On Fri, Sep 28, 2012 at 7:25 PM, Anthony Scopatz wrote:
> On Fri, Sep 28, 2012 at 7:44 PM, Fernando Perez wrote:
>
>> On Fri, Sep 28, 2012 at 3:11 PM, Charles R Harris
>> wrote:
>> > Bitch, bitch, bitch. Look, I know you are pissed and venting a bit, but
>> this
>> > problem could have been dete
On Fri, Sep 28, 2012 at 6:44 PM, Fernando Perez wrote:
> On Fri, Sep 28, 2012 at 3:11 PM, Charles R Harris
> wrote:
> > Bitch, bitch, bitch. Look, I know you are pissed and venting a bit, but
> this
> > problem could have been detected and reported 6 months ago, that is,
> unless
> > it is new du
On Fri, Sep 28, 2012 at 7:44 PM, Fernando Perez wrote:
> On Fri, Sep 28, 2012 at 3:11 PM, Charles R Harris
> wrote:
> > Bitch, bitch, bitch. Look, I know you are pissed and venting a bit, but
> this
> > problem could have been detected and reported 6 months ago, that is,
> unless
> > it is new du
On Fri, Sep 28, 2012 at 3:11 PM, Charles R Harris
wrote:
> Bitch, bitch, bitch. Look, I know you are pissed and venting a bit, but this
> problem could have been detected and reported 6 months ago, that is, unless
> it is new due to development on your end.
It would be great if we could keep thes
Gael puts in a plea for backward compatibility; I totally agree.
Numpy sometimes goes out of its way to make this hard. For example, when the
syntax of histogram were changed you got a nice DepreciationWarning about an
option to switch to the new behaviour; great. But a few releases later tha
On Sep 28, 2012, at 4:53 PM, Henry Gomersall wrote:
> On Fri, 2012-09-28 at 16:43 -0500, Travis Oliphant wrote:
>> I agree that we should be much more cautious about semantic changes in
>> the 1.X series of NumPy.How we handle situations where 1.6 changed
>> things from 1.5 and wasn't reporte
On Fri, Sep 28, 2012 at 3:23 PM, Gael Varoquaux <
gael.varoqu...@normalesup.org> wrote:
> Hi numpy developers,
>
> First of all, thanks a lot for the hard work you put in numpy. I know
> very well that maintaining such a core library is a lot of effort and a
> service to the community. But "with g
On Fri, 2012-09-28 at 16:43 -0500, Travis Oliphant wrote:
> I agree that we should be much more cautious about semantic changes in
> the 1.X series of NumPy.How we handle situations where 1.6 changed
> things from 1.5 and wasn't reported until now is an open question and
> depends on the partic
Thank you for expressing this voice, Gael.It is an important perspective.
The main reason that 1.7 has taken so long to get released is because I'm
concerned about these kinds of changes and really want to either remove them or
put in adequate warnings prior to moving forward.
It's a lon
Hi numpy developers,
First of all, thanks a lot for the hard work you put in numpy. I know
very well that maintaining such a core library is a lot of effort and a
service to the community. But "with great dedication, comes great
responsibility" :).
I find that Numpy is a bit of a wild horse, a mo
Hi everyone,
The PyData NYC team and Continuum Analytics are proud to announce the full
lineup of talks and speakers for the PyData NYC 2012 event! We're thrilled
with the exciting lineup of workshops, hands-on tutorials, and talks about
real-world uses of Python for data analysis.
http://nyc201
In [19]: u = np.arange (10)
In [20]: v = np.arange (10)
In [21]: u[v] = u
In [22]: u[v] = np.arange(11)
silence...
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Fri, Sep 28, 2012 at 9:45 AM, Nathaniel Smith wrote:
> Hi all,
>
> I've gotten a pull request for scikits-sparse to switch it to using
> numpy.distutils:
> https://github.com/njsmith/scikits-sparse/pull/2
>
> Overall this seems fair enough, finding libraries is a pain and
> numpy.distutils ha
Hi,
On Fri, Sep 28, 2012 at 3:45 PM, Nathaniel Smith wrote:
> Hi all,
>
> I've gotten a pull request for scikits-sparse to switch it to using
> numpy.distutils:
> https://github.com/njsmith/scikits-sparse/pull/2
>
> Overall this seems fair enough, finding libraries is a pain and
> numpy.distuti
Hi all,
I've gotten a pull request for scikits-sparse to switch it to using
numpy.distutils:
https://github.com/njsmith/scikits-sparse/pull/2
Overall this seems fair enough, finding libraries is a pain and
numpy.distutils has that knowledge.
1) What's the proper way to find lapack using numpy.
On Fri, Sep 28, 2012 at 1:48 AM, Ralf Gommers wrote:
> Looks great! After a quick browse, the only thing I noticed that still needs
> some thought is the color scheme for the labels.
That's easy to adjust afterwards.
___
NumPy-Discussion mailing list
Nu
18 matches
Mail list logo
