[SciPy-Dev] preparing for scipy 0.8 release
Thu Apr 29 22:08:28 CDT 2010
On Tue, Apr 27, 2010 at 10:30 PM, Ralf Gommers
> On Mon, Apr 26, 2010 at 7:41 PM, Ralf Gommers <email@example.com>
>> On Mon, Apr 26, 2010 at 6:44 AM, Pauli Virtanen <firstname.lastname@example.org> wrote:
>>> Sun, 25 Apr 2010 19:05:27 +0800, Ralf Gommers wrote:
>>> As David said, we'll need at least Numpy >= 1.4, due to use of npymath.
>>> It might be difficult to go for Python 3 support if we want to have
>>> backwards compatibility with Numpy 1.4, unless we go really ugly and
>>> start duplicating some of the utility functions inside Scipy. But from a
>>> maintenance POV that might be less of a burden than having to maintain
>>> 0.8.x and 0.9.x simultaneously...
>> The number of fixes in the 0.7 series is small, so I'm not sure if the
>> maintenance burden is really that high (besides possibly having to do an
>> extra maintenance release). It depends on how long you'd want to keep
>> compatibility with numpy 1.4. Anyway, both options sound better than having
>> no compatible release at all.
> I thought about it some more, and a backwards compatible release with numpy
> 1.4.1 that is also compatible with numpy 2.0 is not even possible. And
> compatibility with 1.4.0 is not nearly as useful. So two releases would
> really make sense: 0.8 built against numpy 1.4.1 and 0.9 against numpy 2.0
> with py3k compatibility.
> Here's a proposal for the release schedule:
> 30/05: create 0.8.x branch, beta available, trunk open to add py3k
> 11/06: 0.8 release candidate 1
> 22/06: 0.8 release
> 15/08: create 0.9.x branch, first beta
> 22/08: 0.9 release candidate 1
> 01/09: 0.9 release
> How does this sound?
Sounds good to me, but it means numpy 2.0 has to be out soon too (its
release schedule should be earlier than scipy, the earlier the
More information about the SciPy-Dev