Table of Contents | ||||
---|---|---|---|---|
|
The Python Shell integration requires Python releases 3.7 onwards and the installation of Python.NET.
Setup Steps:
1. Install Python and Python.NET in the machines where you run the application and on those using the Solution Designer.
2. Configure the Solution Settings to select the appropriate Python shell folder.
Each solution can specify its own Python interpreter, facilitating the development and maintenance of different solutions that may require different Python versions.
title | Click here to expand on how to Install Python |
---|
You can download Python here.
Check the Use admin privileges checkbox, and select Customize installation.
During the installation of the Python Engine,select the option to “Install for all users”.
If You install Python under your local user, you may have issues when running the solution as a service, or when deploying the solution for production.
Tip |
---|
This image may be slightly different for your Python version, but always enable the options equivalent to:
Especially in the production server.
|
Once you've downloaded, open the command prompt as an ADMINISTRATOR and type “pip install pythonnet”. For this work, you'll need internet access. If internet is not available, download and install manually.
Once Python.NET has been installed, you can start using Python in your solution.
Note |
---|
Note: For Python versions above 3.12, Pythonnet is not available. For more information, visit their documentation. |
Feature | Benefit | Use Case |
---|---|---|
Independent Python Versions | Each solution uses its own interpreter | Library compatibility management |
Solution-Contained Scripts | Scripts stored in .dbsln database | Simplified deployment and IP protection |
Output Playground | Interactive execution in designer | Testing and development |
C#/Python Interop | Call methods across languages | Call methods across languages |
title | Click here to expand on how the setup the Python location in the Designer |
---|
Python Interpreter | |
---|---|
Local | Defines the path of the Python installation folder on the local machine. |
Server | Defines the path of the Python installation folder on the remote server. |
Once you've installed Python, you can take a look at our Python demo with code examples.
→ Learn more at Python Example.The Python Example illustrates how to use the Python and .NET languages for the Scripts.
This section presents a summary of that information, listing the modules in the solution where Python code can be used.
The Code Behind for the displays can be written in C#, VB.NET or JavaScript, not Python directly. But from the CodeBehind you can call tasks and methods, which can be written in Python.
This integration allows you to execute Python code from external files. Just create a Script Task with the following code:
Code Block | ||||
---|---|---|---|---|
| ||||
# This code call the execution of the external file using Python Shell # with the optional args defined in this initial section # # The macro _ExecutionPath_ is replaced by the path where the solution is set to execute # Replace that macro by a specific path, or user other built-in macros as nedded # arg1 = @Tag.Tag1 arg2 = @Tag.Tag2 result = TK.ExecutePythonShell("_ExecutionPath_ExternalSum.py", [arg1, arg2]) @Tag.Result = result |
Tip | ||
---|---|---|
| ||
Any Python scripts you create in Scripts / Tasks can be edited and tested in Scripts / Code Editor. To test your script, click on [Monitor Icon] in the top toolbar. This will run your code and display messages in the Output Window, under the script editor. This integration will work if your Python version is 3.7 or newer, with Python.NET installed, and the executable is correctly mapped in Solution / Settings. |
The code editor can be accessed through Scripts / Code Editor.
When the editor is used to edit Script Tasks, you can test the scripts directly, using the Play button at the Task name line. The results of your code will show in the standard Designer output.
The access to tags and other properties for other models is exactly the same as C# or VB.NET; just use the '@' symbol to access the properties directly, as shown in the image: '@Tag.Tag1'.
In the Script, or in any place in your solution where Expressions are allowed, you can use the following syntax to call classes.
Code Block | ||
---|---|---|
| ||
@Script.Class.TestClass.ExempleMethod(param1, param2) |
This activation is independent of the language the class was created in.
This means C# and VB.NET can call Python classes, and Python code can call .NET classes.
In this section:
Page Tree | ||
---|---|---|
|