-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
move process utilities to jupyterlab_launcher #4696
Conversation
from jupyterlab.process import which | ||
from jupyterlab.process_app import ProcessApp | ||
from jupyterlab_launcher.process import which | ||
from jupyterlab_launcher.process_app import ProcessApp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the kind of clear indication that the functionality of which and ProcessApp belong outside of jupyterlab, since otherwise this standalone example services package still has a dependency on all of jupyterlab.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good point.
This cannot be merged until a new version of jupyterlab_launcher is released. /cc @jasongrout |
A release is ready to go, just waiting on permission to upload it. |
The pypi release of jupyterlab_launcher 0.11, with these changes, is uploaded, and the conda-forge release is in-process: conda-forge/jupyterlab_launcher-feedstock#33 |
Restarted the tests now that the pypi release is out. |
I think we should hold off merging this until just before our next pre-release, since it forces everyone to update jupyterlab_launcher. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome. Thank you, @ivanov!
The companion to jupyterlab/jupyterlab_server#44