[IPython-dev] How to handle extensions
Wed Oct 14 18:20:17 CDT 2009
I finished up the pretty extension. Everything seems to work fine. Do you
to try this branch out before I merge it into trunk?
On Tue, Oct 13, 2009 at 8:26 AM, Robert Kern <email@example.com> wrote:
> On 2009-10-13 03:14 AM, Hans Meine wrote:
> > On Friday 09 October 2009 20:00:59 Brian Granger wrote:
> >> - If an extension/profile can be distributed as a third party package,
> >> should be. Thus,
> >> the custom completer for enthough.traits should ship with
> >> Things related
> >> to numpy should ship with numpy.
> > Although this sounds good, one needs to make sure that this does not
> > installation problems. E.g. if the ipython extension is only installed
> > ipython is found, the installation order may suddenly become relevant.
> > Or packagers may start to make the extension optional (e.g. with Gentoo
> > flags, or by putting them into an additional package), which would make
> > less convenient for the user IMO.
> Packagers simply shouldn't do that. Optional components == bad news.
> > Finally, I would expect "import numpy" to activate all relevant
> extensions in
> > ipython (otherwise, where's the convenience?), but then we need to put
> > into 3rd party packages to check for the IPython runtime - would that be
> > design?
> I would really hope that packages wouldn't do that. Even if I have the
> I may not want their extensions.
> Robert Kern
> "I have come to believe that the whole world is an enigma, a harmless
> that is made terrible by our own mad attempt to interpret it as though it
> an underlying truth."
> -- Umberto Eco
> IPython-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev