On Tue, Jun 26, 2018 at 1:26 AM Travis Oliphant <teoliph...@gmail.com> wrote:
> I like the proposal generally. NumPy could use a good orthogonal indexing > method and a vectorized-indexing method is fine too. > > Robert Kern is spot on with his concerns as well. Please do not change > what arr[idx] does except to provide warnings and perhaps point people to > new .oix and .vix methods. What indexing does is documented (if hard to > understand and surprising in a particular sub-case). > > There is one specific place in the code where I would make a change to > raise an error rather than change the order of the axes of the output to > provide a consistent subspace. Even then, it should be done as a > deprecation warning and then raise the error. > > Otherwise, just add the new methods and don't make any other changes until > a major release. > I'd suggest that the NEP explicitly disclaim deprecating current behavior. Let the NEP just be about putting the new features out there. Once we have some experience with them for a year or three, then let's talk about deprecating parts of the current behavior and make a new NEP then if we want to go that route. We're only contemplating *long* deprecation cycles anyways; we're not in a race. The success of these new features doesn't really rely on the deprecation of current indexing, so let's separate those issues. -- Robert Kern
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
