You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newly launched ipcluster instances don't execute code from the variable c.IPEngineApp.startup_command . Min suggested that this is from the new forked Kernel implementation, which doesn't share the startup config.
This change means that all your startup/exec_lines config is inherited by engines.
should be backported for 0.13.1, because engine startup code is impossible to configure in 0.13.
The real long-term fix for this is to make IPEngineApp a subclass of IPKernelApp, but this should be an adequate band-aid until then.
closes#2213
use KernelApp.exec_lines/files in IPEngineApp
This change means that all your startup/exec_lines config is inherited by engines.
The real long-term fix for this is to make IPEngineApp a subclass of IPKernelApp, but this should be an adequate band-aid until then.
closesipython#2213
Newly launched ipcluster instances don't execute code from the variable c.IPEngineApp.startup_command . Min suggested that this is from the new forked Kernel implementation, which doesn't share the startup config.
More context: http://mail.scipy.org/pipermail/ipython-user/2012-July/010769.html
The text was updated successfully, but these errors were encountered: