Manage ggsql kernel spec in Positron extension#277
Open
georgestagg wants to merge 5 commits intomainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
By managing the kernel spec installation in the Positron extension, we avoid needing to run
ggsql-jupyter --installmanually.Checks for existing
ggsql-jupyterinstallations in well-known user/system Jupyter kernel paths, and in the destination locations used by the ggsql installer.Also adds some required Apple entitlements for running duckdb from a signed macOS package. Not strictly related to this PR but an issue I discovered in testing the above with a relatively simple fix.