[Numpy-discussion] Making numpy sensible: backward compatibility please
Fri Sep 28 21:22:28 CDT 2012
> > >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 follow
> > and I don't believe that it is possible for many of us to monitor the
> > discussions. Also, putting more emphasis on backward compatibility is
> > possible. For instance, the 'order' parameter added to np.copy could have
> > defaulted to the old behavior, 'K', for a year, with a
> > DeprecationWarning, same thing for the casting rules.
> Maybe it still can, but you have to tell us details :-)
> In general numpy development just needs more people keeping track of these things. If you want to keep an open source stack functional sometimes you have to pay a tax of your time to making sure the levels below you will continue to suit your needs.
Thanks for the thorough and thoughtful response. Well spoken...
> > Thank you for reading this long email. I don't mean it to be a complaint
> > about the past, but more a suggestion on something to keep in mind when
> > making changes to core projects.
> > Cheers,
> > Gaël
> > ____
> >  https://github.com/scikit-learn/scikit-learn/commit/7842748cf777412c506a8c0ed28090711d3a3783
> >  http://mail.scipy.org/pipermail/numpy-discussion/2012-September/063985.html
> >  http://mail.scipy.org/pipermail/numpy-discussion/2012-July/063126.html
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion@scipy.org
> > http://mail.scipy.org/mailman/listinfo/numpy-discussion
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion