[Numpy-discussion] planning for numpy 1.3.0 release

Charles R Harris charlesr.harris at gmail.com
Tue Sep 9 06:45:15 EDT 2008


On Mon, Sep 8, 2008 at 11:54 PM, David Cournapeau <
cournapeau at cslab.kecl.ntt.co.jp> wrote:

> On Mon, 2008-09-08 at 17:12 -0700, Jarrod Millman wrote:
> > Now that 1.2.0 is almost finalized, I wanted to ask everyone to start
> > thinking about what they plan to work on for the next minor release:
> > http://scipy.org/scipy/numpy/milestone/1.3.0
> >
> > We have been gradually moving toward a more time-based release
> > schedule over the last several months.  In this vein, I would like to
> > move feature and code discussion and planning to the beginning of the
> > release cycle, rather than waiting until the end of the release cycle.
> >  So if there is something that you would like to work on during this
> > release cycle, please bring it up now.
> >
> > Also it is important for us to keep the trunk as stable as possible;
> > if you wish to work on a major new feature or an significant
> > refactoring of the codebase, please work in a branch.
>
> Hi Jarrod, hi everyone,
>
>        Here are some things I would like to work/seen fixed on for 1.3:
>                - fix VS 2003 compilation for mtrand.c (numpy is not
> buildable with VS
> 2003.2005.2008 ATM because of a compiler limitation)
>                - clean umathmodule (work almost done in the clean_math
> branch, still
> need some testing on windows and solaris before merging).
>

I also have a big rearrangement/cleanup of the inner loops in the
umathmodule that has been sitting around for half a  year. I think it is
almost orthogonal to your work because it deals with a different part of the
code.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20080909/e869d9c8/attachment.html>


More information about the NumPy-Discussion mailing list