[SciPy-dev] a modest proposal for technology previews
Thu Nov 6 06:11:06 CST 2008
On Thu, Nov 6, 2008 at 3:15 AM, Nathan Bell <email@example.com> wrote:
> On Wed, Nov 5, 2008 at 11:53 AM, David Cournapeau <firstname.lastname@example.org> wrote:
>> Except it doesn't. Putting it into scipy does not make it magically
>> built and released. Again, the last release of scipy was in september
>> 2007. As I pointed out previously, putting code into scipy makes it
>> *more* difficult to distribute, at least in practice.
> Well, that's (1) not true today since 0.7 is due
This is not true for scipy.spatial, but this will be true if we follow
the same workflow for every package. More code means more work, it is
as simple as that.
> and (2) another
> problem that needs to be addressed (e.g. by moving to a 6 month
Yes, I also want more regular scipy releases. But adding more code
makes it less likely. Adding code has a cost on the release
management, unless we have a fairly restricted window for getting
changes, which would then be against the whole point of putting the
new code in scipy.
> Let's release SciPy 0.7 (w/ spatial) ASAP and then look towards making
> scikits a more viable alternative.
Yes, that's the plan I want to follow. 0.7 will of course be released
with scipy.spatial, I don't think anyone has ever been arguing for the
More information about the Scipy-dev