On Jan 17, 2016, at 1:12 AM, Volker Braun <[email protected]> wrote: > > IMHO the app should just start and manage its own jupyter server; Launch it > on startup and shut it down when the app is closed. The notebook server > doesn't fork into the background so its trivial to just keep a single > process, no need for a pidfile.
Well, I disagree, but it sounds like it’s the only option. > If the user wants to launch a separate server (maybe with different options) > by hand then he/she should be allowed to. > > PS: > * Always use subprocess over os.system I was planning to use NSTask. :-) > * Jupyter will autoincrement the port if it is in use, don't rely on it using > the given —port Right. > * Race conditions with ports, pids, and filenames are unlikely but often > exploitable security issues. I’ll keep that in mind. -Ivan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
