[SciPy-Dev] linalg.solve keyword deprecation

[josef.pktd at gmail.com]

On Mon, Apr 23, 2018 at 9:23 AM, Pauli Virtanen <pav at iki.fi> wrote:

> ma, 2018-04-23 kello 12:20 +0200, Ilhan Polat kirjoitti:
> [clip: solve(sym_pos=, debug=)]
> > Hence I've proposed to deprecate these in
> > https://github.com/scipy/scipy/pull/8715/files . Pauli also chimed in
> > and
> > mentioned that this might not be a good idea since this is a central
> > function and the benefits might not be worth the effort and backwards
> > compatibility problems. With Python2 dying, I think the backwards
> > compatibility part won't be such important problem anymore and the
> > benefit
> > is that we don't need to have such strange signature.
>
> This I think is relevant:
>
> http://blog.khinsen.net/posts/2017/11/22/stability-in-the-
> scipy-ecosystem-a-summary-of-the-discussion/
>
> My own position is that any breakage should have good reasons behind
> it, and cosmetic reasons (function signature with some duplicated
> functionality) usually are not strong enough.
>
> Re: Python3 --- I think that Python 3 also breaks things should not be
> a permission to break more things.
>


I think even "cosmetic" (confusing signatures) should be cleaned up in the
long run,
otherwise they never go away unless there is a big break release.
But deprecation periods should be long, e.g. > 3 years.

(I had to deprecate three functions in statsmodels because I had misspelled
the function names when writing them.)

Josef



>
>         Pauli
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180423/8aa44888/attachment-0001.html>