Re: [jupyter] Cannot create new notebook within a folder with a [space] in its name

231 views
Skip to first unread message

Matthias Bussonnier

unread,
Feb 18, 2016, 6:29:21 PM2/18/16
to jup...@googlegroups.com

On Feb 18, 2016, at 15:23, Sandbo Chang <sandb...@gmail.com> wrote:

Hi, 

I just realized that there is problem if I am to create a notebook file within any directory which has [space] character in its name.
It doesn't have to be the immediate directory, but anything above it, in between it and the root.

I confirmed by checking the permission in my Linus host and nothing looks fishy, then I tested by doing a few creation and deletion where things just worked fine.
Finally I compared the difference, and then it was the file name containing [space].

Is it a known bug/limitation, or I did something wrong?

Not as far as we know. And it works great at least for me. 
Can you give more info about your platform ?
-- 
M

Thanks for reading.


--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/06f53f27-66eb-4085-b57a-1685c8a35397%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sandbo Chang

unread,
Feb 18, 2016, 6:41:15 PM2/18/16
to Project Jupyter
Sorry I removed my initial post, as I found that it has nothing to do with [space] with further testing.
I am running Jupyter notebook server for Python, on a remote server that I have admin right on Fedora 23.

I am not setting to start my Jupyter notebook server with a user, which prior to that I was playing around starting the server as root.
It was that when the server was run using root, it created some .ipython checkpoint folder as root, which now is preventing me from modifying them.
Manually remove the root-owned .ipython checkpoint folder solved the problem.
Reply all
Reply to author
Forward
0 new messages