jupytext interferes with sudospawner operation
See original GitHub issueI did not investigate further, but after installing jupytext I cannot spawn single-user notebook servers anymore.
A …/bin/pip uninstall jupytext
followed by a restart of the jupyterhub service solves the problem.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Frequently Asked Questions - Jupytext documentation
Jupytext is a Python package that provides two-way conversion between Jupyter notebooks and several other text-based formats like Markdown documents or ...
Read more >Jupyter Documentation - Read the Docs
Try Jupyter (https://try.jupyter.org) is a site for trying out the Jupyter Notebook, equipped with kernels for several.
Read more >Cannot run jupyterhub with Sudospawner - Stack Overflow
I can run jupyterhub for single user successfully but when I add c.JupyterHub.spawner_class = 'sudospawner.SudoSpawner' it throws an error -
Read more >Explaining how to use Jupytext for collaborative ... - YouTube
Got it. Explaining how to use Jupytext for collaborative editing of notebooks with Git. 1.1K views 1 year ago. Gary Steele. Gary Steele....
Read more >The Jupyter+git problem is now solved - Fast.ai
With nbdev2, the problem has been totally solved. ... Jupytext saves notebooks in a line-based format, instead of in JSON.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If it’s Debian / APT, you can use my Debian packaging to get it all in one fancy box.
Yes I’m running into this problem, and I’ve found the cause. sudospawner specifies the port that the web extension should run and also sets port_retries to 0 to prevent the web notebook from finding alternative ports.
When jupyterlab initializes it takes the port, and when jupytext initializes it uses the same port and causes an error. What should happen is when jupytext initializes, the system should try to assign a random port.
Also this seems to be a new error, that just appeared in the last few days.