Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't trigger startup code in Engines #2213

Closed
matthewturk opened this issue Jul 27, 2012 · 0 comments · Fixed by #2214
Closed

Can't trigger startup code in Engines #2213

matthewturk opened this issue Jul 27, 2012 · 0 comments · Fixed by #2214

Comments

@matthewturk
Copy link

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 as completed in 2ff8a90 Jul 29, 2012
minrk added a commit that referenced this issue Jul 29, 2012
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
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
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.

closes ipython#2213
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants