IPython 0.11 configuration not loaded

[matveym]

In IPython profile colors='Linux', in django shell colors='LightBG'.

See path for the fix.

[nbr]

The patch seems to help, for me at least. (Python 2.6.1, Django 1.3.1, IPython 0.11, osx.)

[Aymeric Augustin]

Considering:

• ​IPython's embedding docs,
• the fact that embed basically calls load_default_config and runs a TerminalInteractiveShell — ​see the source,
• the discussions on #16483,

I think we should simply call embed, as demonstrated in attached patch.

Could someone who's familiar with IPython confirm?

[Aymeric Augustin]

The last comment on #16483 suggests that IPython.embed has some issues, but it links to a ticket that doesn't mention embed.

Given the number of options that exist to embed an IPython shell, and that each technique appears to have advantages and drawbacks, I'm now leaning towards using the simplest API -- ie. IPython.embed -- and let the IPython developers sort out their bugs if there are any.

[Chris Beaven]

​The ticket has been resolved, and in the resolution embed is mentioned.
So this is fixed in 0.12 (which has been released), but if we change it like this we're breaking it for people who still have 0.11. Is this acceptable?

[Aymeric Augustin]

Yes, I think that's acceptable.

IPython is only useful in a development environment, where people can get any version they need, and even isolate it with virtualenv if necessary.

[Jacob]

In [17379]:

Fixed #17078: properly invoke IPython 0.12.

[Jacob]

In [17380]:

[1.3.X] Fixed #17078: properly invoke IPython 0.12.

Backport of r17379.

[Paul Egan]

Sorry for commenting on a closed ticket but I thought it worth pointing out that using embed has additional affects.

The default config (e.g. created with ipython profile create) uses settings such as c.TerminalInteractiveShell.colors but these do not apply to an embedded shell. You need to use InteractiveShellEmbed or InteractiveShell configuration settings to change the appearance of a django shell started with embed.

Also using embed like this mean that there's no hook to load extensions or specify other app settings like exec_lines or exec_files (configured with InteractiveShellApp).

Instead of using embed, it might be better to use a similar pattern as used for the ipython command itself:

from IPython.frontend.terminal.ipapp import TerminalIPythonApp
app = TerminalIPythonApp.instance()
app.initialize(argv=[])
app.start()

[Aymeric Augustin]

An IPyhton dev chimed in with a similar pull request: ​https://github.com/django/django/pull/512

The previous resolution wasn't optimal, I think it's worth revisiting this.

[Ramiro Morales]

#18204 was closed as duplicate.

[Ramiro Morales <cramm0@…>]

In 3570ff734e93f493e023b912c9a97101f605f7f5:

Fixed #17078 -- Made shell use std IPython startup.

This allows for a behavior more in line with what is expected by Ipython
users, e.g. the user namespace is initialized from config files, startup
files.

Thanks Benjamin Ragan-Kelley from the IPython dev team for the patch.