Skip to content

Can't trigger startup code in Engines #2213

Closed
MatthewTurk opened this Issue Jul 27, 2012 · 0 comments

2 participants

@MatthewTurk

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

@minrk minrk closed this in 2ff8a90 Jul 29, 2012
@minrk minrk added a commit that referenced this issue Jul 29, 2012
@minrk minrk Backport PR #2214: use KernelApp.exec_lines/files in IPEngineApp
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
b1241d5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.