[Work in Progress] Connect Jupyter comm from kernel to frontend #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes the kernel extension in favor of a simple python module that is invoked before starting the
SparkSession
.This avoids injecting a variable into the user namespace, and fixes race conditions with restarting the kernel
For SWAN this would mean that instead of installing a kernelextension, we add a step to the sparkconnector to configure the monitor and connect the kernel to the frontend (potentially here)
TODO
Related to #7