ipython/ipython — pull request #1939 by minrk (2012-06-13 07:48:25+00:00)
Title: Namespaces

This is the first step towards #1537

Further (more important) things I haven't worked out yet:

1. single import for all display-related functions (currently in core.display, lib.display)
2. InteractiveShellEmbed, InteractiveShell, etc. somewhere so that simple entry points / handles are readily accessible.

Possible options:

1. top-level IPython.display has all our display apis
2. IPython.api defines our general public interface - display, anything else
3. IPython.api is a *package*, where we put various categorized public APIs (e.g. IPython.api.display)

Any suggestions? This seems a pretty general issue we have, where we haven't really thought about public APIs at all, aside from magics and methods on the InteractiveShell object. Users need to be much too familiar with our code layout to use it.