Split expression and python scripting packages #942
Merged
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 PR splits expression and Python scripting into separate packages. These two packages represent very different approaches to scripting, with totally different and unrelated dependencies. Given the possibility of C# scripting and more flexible uses of expression scripting, the Python dependencies are not so necessary in modern workflows.
An important goal of the PR is to maintain backwards compatibility with existing workflows while facilitating porting of code to use the new packages. Scripting editors have also been split into a separate design package, in line with the architecture of other packages, in order to more easily enable running of workflows from the command-line.
Fixes #732