[Numpy-discussion] A roadmap for NumPy - longer term planning
harrigan.matthew at gmail.com
Fri Jun 1 13:11:54 EDT 2018
I would love to see gufuncs become more general. Specifically I would like
an optional prologue and epilogue function. The prologue could potentially
1) inspect parameterized dtypes 2) kwargs 3) set non-trivial output array
sizes 4) initialize data structures 5) defer processing to other functions
(BLAS). The epilogue function could do any clean up of data structures.
On Fri, Jun 1, 2018 at 12:57 PM, Stefan van der Walt <stefanv at berkeley.edu>
> Hi Ralf,
> On Thu, 31 May 2018 21:57:06 -0700, Ralf Gommers wrote:
> > - "internal refactorings": MaskedArray yes, but the other ones no.
> > numpy.distutils and f2py are very hard to test, a big refactor pretty
> > guarantees breakage. there's also not much need for refactoring, because
> > those things are not coupled to the numpy.core internals. numpy.financial
> > is simply uninteresting - we wish it wasn't there but it is, so now it
> > simply stays where it is.
> I want to clarify that in the current notes we put down ideas that
> prompted active discussion, even if they weren't necessarily feasible.
> I feel it is important to keep the conversation open to run its course
> until we have a good understanding of the various issues at hand.
> You may find that, in person, people are more willing to admit to their
> support for some "heretical" ideas than they are here on the list.
> E.g., you say that the financial functions "now simply stay", but that
> promises a future of a NumPy that never shrinks, while there is
> certainly some support for allowing NumPy to contract so that we can
> release maintenance burden and allow development of other core areas
> that have been neglected for a long time.
> You will *always* have small, vocal proponents of any specific piece of
> functionality; that doesn't necessarily mean that such functionality
> contributes to the health of a project as a whole.
> So, I gently urge us carefully reconsider the narrative that nothing can
> change/be removed, and evaluate each suggestion carefully, not weighing
> only the very evident negatives but also the longer term positives.
> Best regards,
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion