Kernels should start in notebook dir when manually specified #1985
Comments
|
See PR #1951 |
|
Your time machine is even better than mine! |
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this issue
Nov 3, 2014
minor notebook startup/notebook-dir adjustments * change inaccurate / distressing "Overwriting profile..." log message * `ipython notebook path` results in setting notebook-dir if it's a dir, rather than unconditionally setting file-to-run * file-to-run overrides no-browser * kernels start in the notebook dir, rather than the Server's cwd * notebook dir is validated, and created if it doesn't exist (only if parent exists, like ~all other such things) closes ipython#1985 closes ipython#1980
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the --notebook-dir flag only sets the saving directory, but kernels still start wherever the notebook process was started. For consistency, if the notebook dir flag was given, it should also apply to the kernel directories, otherwise it's a bit useless, and makes it clumsy to run isolated servers configured with directories for their own profiles.
This is easy but I think we should make it a blocker for 0.13 so that there's at least some consistent mechanism for mild user isolation out of the box.
The text was updated successfully, but these errors were encountered: