Added NumExprCapability to VCell Expressions#1649
Merged
CodeByDrescher merged 2 commits intomasterfrom Mar 12, 2026
Merged
Conversation
ec6a326 to
534a40c
Compare
jcschaff
approved these changes
Mar 12, 2026
Member
jcschaff
left a comment
There was a problem hiding this comment.
looked through the changes, everything looks good. approved.
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
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.
Turns out, we need to support the expression grammar of the python library
numexpr, which is different from normal python grammar that is valid for python'seval().