On Mon, Sep 2, 2013 at 8:53 AM, Juan Luis Cano <juanlu...@gmail.com> wrote: > > The subject speaks for itself, I was diving into NumPy source code and > saw some NEPs, and I wonder if there still function as a mechanism to > propose changes to NumPy, and if it is documented somewhere.
Yes, the NEP "process", such as it is, is still a mechanism for proposing some kinds of changes to numpy, but it's not the only one. Generally, it's only needed for sweeping changes or ones that require significant amounts of considered design and choosing between close alternatives. Most changes do not fall into this category. The process itself is not really documented, per se. Post what you are thinking about to the mailing list. The discussion may reach a point where someone says, "Hey, it would be a good idea to write all this up into a NEP". Then you write a NEP. Alternative designs are documented and discussed, one is chosen, implementations are made, PRs are merged. Or not. If you want information about how to format a NEP and what to include, consult PEP 1 and PEP 12, as we stole this process from the core Python development team: http://www.python.org/dev/peps/pep-0001/ http://www.python.org/dev/peps/pep-0012/ -- Robert Kern
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion