[SciPy-Dev] Summarizing the scikit-signal discussion
Fri Jan 13 09:34:24 CST 2012
On Fri, Jan 13, 2012 at 4:19 PM, Bruce Southey <firstname.lastname@example.org> wrote:
> I am curious why you want to jump to a 'scikit' approach especially with
> the usage and power of git.
I think some points that were mentioned previously about the advantage
of a seperate scikit is that allows a faster release cycle for getting
binary installers to end users (not tied to slower scipy releases) and
that it allows more exploratory API development (without being tied to
conservative scipy deprecation policy).
> If the goal is to improve and extend parts of scipy, then a scikit is
> only useful for code that has a different license than scipy. It would
> be more effective to just create a new git branch. That way changes can
> be easily integrated back into scipy as well as maintaining the changes
> in numpy/scipy. More importantly, other scipy-dependent projects can
> move and replace relevant code (assuming appropriate licensing) into
> that branch thus avoiding any new dependencies in those projects.
> Thus, just branch scipy, add your code (including tests and
> documentation) and provide guidance/leadership on how different pieces
> that people contribute can be incorporated.
> SciPy-Dev mailing list
More information about the SciPy-Dev