Aaaand looking at it more it looks like maybe I will have to wait for the /api/shutdown thing. Surprisingly, until that change, there seems to be no reliable way to shut down the notebook server at all (at least on Windows) except physically pressing Ctrl-C in the console window. This is because on Windows there's (apparently) no such thing as SIGINT, and SIGTERM just kills without raising any interrupt. So I can kill the notebook process that way, but it doesn't exit cleanly; for instance, it leaves its nbserver file behind, so that "jupyter notebook list" forever after will show that old server unless I manually delete the file. Quite strange that this apparently hasn't been an issue for anyone until now. Anyway I guess I'll just wait with bated breath for the 5.1 release.
-- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/fe497a8e-7a78-40bd-8de7-0d51dbec4335%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
