On Sat, Oct 12, 2019 at 9:58 AM Ralf Gommers <[email protected]> wrote:
> > > On Sat, Oct 12, 2019 at 3:21 AM Charles R Harris < > [email protected]> wrote: > >> Hi All, >> >> Thought I'd raise the option of trying to put together an NEP for the >> 1.18 release like Python does PEPs. If that is considered too procedural >> for releases that come out every six months or so, are there any >> suggestions for an alternative? >> > > The Python one only contains a release schedule, and gets updated later > with a small subset of the release notes: > https://www.python.org/dev/peps/pep-0494/. I guess its main audience is > packagers and companies needing to plan ahead supporting a new Python > version. > > What would you like to put in such a NEP? > > >> About 1.19 itself, I expect to fork 1.18.x in the middle of next month >> aiming at a release in late December. The main task I currently see for >> 1.19 is to remove the shims for Python 2.7 and 3.5, there are already a >> couple of delayed PRs along that line. If there are other things that folks >> think should be on the todo list, suggestions are welcome. >> > > For 1.18 I think the main things are further changes to numpy.random and > the dispatch system. For 1.19 not sure, that still feels far away. > Agree about numpy.random. What changes are you looking for in the dispatch system? Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] https://mail.python.org/mailman/listinfo/numpy-discussion
