On Sat, Jul 21, 2018 at 5:46 PM, Hameer Abbasi
wrote:
> The possibility of another major version change (possibly the same one)
> where we re-write all portions that were agreed upon (via NEPs) to be
> re-written, with a longer LTS release (3 years? 5?).
>
> I’m thinking this one could be similar
On Sat, Jul 21, 2018 at 4:48 PM, Ralf Gommers wrote:
> Hi all,
>
> Here is a first draft of a NEP on backwards compatibility and deprecation
> policy. This I think mostly formalized what we've done for the last couple
> of years, however I'm sure opinions and wish lists will differ here.
Oh *awes
Agreed that changes better be gradual, and that we do not have the manpower
to do otherwise (I was slightly shocked to see that my 94 commits in the
last two years make me the fourth most prolific contributor in that
period... And that is from the couple of hours a week I use while
procrastinating
Hi Ralf,
Maybe as a concrete example of something that has been discussed, for which
your proposed text makes (I think) clear what should or should not be done:
Many of us hate that `np.array` (like, sadly, many other numpy parts)
auto-converts anything not obviously array-like to dtype=object, a
>
>- We enforce good practices in our code. For example, we will
> explicitly disallow subclassing from ndarray, we get rid of scalars, we
> fix
> the type system.
>
>
> Given my other reply, probably no surprise that I strongly disagree with
the idea of disallowing subclasses. But
Hi Ralf,
Overall, this looks good. But I think the subclassing section is somewhat
misleading in suggesting `ndarray` is not well designed to be subclassed.
At least, for neither my work on Quantity nor that on MaskedArray, I've
found that the design of `ndarray` itself was a problem. Instead, it
On Sat, Jul 21, 2018 at 5:46 PM, Hameer Abbasi
wrote:
> Hello,
>
> Very well written article! It takes a lot of important things into
> account. I think a number of things should be mentioned, if only in the
> alternatives:
>
>- One major version number change, with lots of “major version cha
Hello,
Very well written article! It takes a lot of important things into account.
I think a number of things should be mentioned, if only in the alternatives:
- One major version number change, with lots of “major version change”
deprecations grouped into it, along with an LTS release.
Hi all,
Here is a first draft of a NEP on backwards compatibility and deprecation
policy. This I think mostly formalized what we've done for the last couple
of years, however I'm sure opinions and wish lists will differ here.
Pull request: https://github.com/numpy/numpy/pull/11596
Rendered versi
Hi all,
Not everyone may be on a NumFOCUS mailing list or read Planet SciPy/Python,
so I thought it'd be good to point this out:
https://www.numfocus.org/blog/numfocus-to-hold-2018-elections-for-board-of-directors
>From my perspective, it would be great to see some candidates who are
actively inv
10 matches
Mail list logo
