[IPython-dev] How to handle extensions

Robert Kern robert.kern@gmail....
Tue Oct 13 10:26:53 CDT 2009


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, it
>> should be.  Thus,
>> the custom completer for enthough.traits should ship with enthought.traits.
>> Things related
>> to numpy should ship with numpy.
>
> Although this sounds good, one needs to make sure that this does not create
> installation problems.  E.g. if the ipython extension is only installed if
> ipython is found, the installation order may suddenly become relevant.
> Or packagers may start to make the extension optional (e.g. with Gentoo USE
> flags, or by putting them into an additional package), which would make things
> 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 code
> into 3rd party packages to check for the IPython runtime - would that be good
> design?

I would really hope that packages wouldn't do that. Even if I have the package, 
I may not want their extensions.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco



More information about the IPython-dev mailing list