WIP Ability to have external code in Python sandbox #6
Conversation
This file contains 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
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.
This is not for review, but just to describe the purpose of the changes in this branch, and in the linked
grist-corebranch https://github.com/gristlabs/grist-core/tree/large-data-python-ext.These allow megagrist code to add python files to be available in per-document sandbox processes. Not fully tested. This branch has a single experiment that replaces dependency graph (
Graph) implementation with one that uses SQLite (using:memory:here). This is much slower than the previous implementation, so this particular experiment may not be interesting. Bigger goal was just to be able to do sandbox things differently in megagrist without affectinggrist-core.