[IPython-dev] Feature and scope creep in IPython

Nicholas Bollweg nick.bollweg at gmail.com
Tue Jan 15 16:48:53 EST 2013

On Tue, Jan 15, 2013 at 1:58 PM, Brian Granger <ellisonbg at gmail.com> wrote:

> One point: while some of our scope and feature creep problems can be
> solved by good workflows and tools, others can't.  I don't think we
> need tools to better manage more and more new features, we need tools
> to help us better manage fewer new features *well*.  And maybe that is
> another way of putting it: I am arguing for quality, not quantity of
> features.
This is a very good point, but since i'm on a kick: what is the means for
determining quality? For the kernel? For the notebook? For the various
frontends? Does every committer weigh in on every decision? What is the
role of non-committers? "Plebiscite" style decision making would probably
be crippling. If a project can start determining what these heuristics are,
maybe the data from its various feeds can help.

I liked some of the discussion on your blog post (I think) by the SymPy
guys: their users "only use 20%" of SymPy... but every user has a different
20%! What is the broader community's usage of IPython like? Has this been
captured before?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20130115/82b3df06/attachment.html>

More information about the IPython-dev mailing list