[SciPy-Dev] preparing for scipy 0.8 release
Sun Apr 25 10:16:36 CDT 2010
On Sun, Apr 25, 2010 at 11:09 AM, Ralf Gommers
> On Sun, Apr 25, 2010 at 9:39 PM, David Cournapeau <firstname.lastname@example.org>
>> On Sunday, April 25, 2010, <email@example.com> wrote:
>> > On Sun, Apr 25, 2010 at 8:21 AM, Gael Varoquaux
>> > <firstname.lastname@example.org> wrote:
>> >> On Sun, Apr 25, 2010 at 09:17:49PM +0900, David Cournapeau wrote:
>> >>> If people think making scipy 0.8.0 python 3.x worths it, it is doable
>> >>> in a short amount of time (that is it won't postpone scipy 0.8.0
>> >>> release).
>> >>> > - Time line: do we want a release before SciPy2010 (end of June)? If
>> >>> > so,
>> >>> > there's only a month left before a freeze.
>> >>> I think this is a good timeline. There has been a lot of new features
>> >>> in scipy, some quite useful (stats, sparse SVD, etc...).
>> > especially also signal (Warren has been very active)
>> >> That last line makes me think that it would be great if it could depend
>> >> on numpy 1.4 rather than numpy 2.
>> > Is it possible to release scipy 0.8 for numpy 1.4, and right after a
>> > scipy 0.9 for numpy 2.0 with the python 3 code merged in ?
>> It is of course possible. But it would mean tha scipy compatible With
>> python 3 would come much later, at least at the current pace (1
>> release per year)
> That pace will go up a bit I hope. If you think that python 3 support could
> be added before June, then it's also possible to do a release without it in
> June, and then 0.9 with it in August or September.
If you manage to do this, I think this will be very useful.
> Even without new features, I think doing two releases (0.8 <-> 1.4.1 and 0.9
> <-> 2.0) is useful. Otherwise there will probably a lot of people who can't
> go to 2.0 yet because they need other libraries/programs that depend on
> numpy 1.4.1, and therefore are stuck with scipy 0.7.2.
> SciPy-Dev mailing list
More information about the SciPy-Dev