IPC transport option not taking effect ? #2722

zemanel opened this Issue Dec 26, 2012 · 1 comment


None yet
2 participants

zemanel commented Dec 26, 2012

Haven't been able to set IPC as transport neither from --transport option or c.IPKernelApp.transport python config file, as tcp is always used.

Been able to force the value on the call stack and use it successfully. Took a look at the code with latest master and ran it through a debugger but wasn't able to figure the configuration system completely or i would had gladly send a patch after confirmation of the issue.

Suspect i can be an issue around the kernel manager factory around:


@minrk minrk referenced this issue Jan 19, 2013


Still more KernelManager cleanup #2811

4 of 4 tasks complete

minrk commented Jan 19, 2013

It works, but the configuration of it was weird, and depended upon how you were starting things. #2811 should make it behave in a more sensible manner (--transport ipc should just work).

@minrk minrk closed this in 8c1236c Jan 24, 2013

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014

Merge pull request #2811 from minrk/ipc_defaults
Still more KernelManager cleanup

Finish up some more work from #2775

closes #2722

- [x] ip/transport configurables only live on KernelManager objects, not ConsoleApp
- [x] fix default ipc paths in `ipython kernel` and `ipython notebook` cases
- [x] fix ipc file cleanup in a few more cases
- [x] add `--transport` alias for all appropriate entry points
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment