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

Don't set current working directory for external kernels #5360

Closed
fayeshine opened this issue Sep 29, 2017 · 2 comments
Closed

Don't set current working directory for external kernels #5360

fayeshine opened this issue Sep 29, 2017 · 2 comments

Comments

@fayeshine
Copy link

current working directory is binded with both ipython console directory and the editor file directory, which is not suitable for remote kernel.
I use a remote kernel (by redirect the port to a external server), and the file directory is totally different for ipython console and my local file directory.
Can we separate these two directory as before or at least add an option to separate them?

@ccordoba12 ccordoba12 added this to the v3.2.5 milestone Sep 29, 2017
@ccordoba12 ccordoba12 changed the title current working directory problem Don't set current working directory for external kernels Sep 29, 2017
@ccordoba12
Copy link
Member

We totally missed this use case. We'll fix it in 3.2.5.

@ccordoba12
Copy link
Member

@rlaverde, please work on this one.

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

No branches or pull requests

3 participants