Settings ExternalToolsSettings/en - Versionsgeschichte

Cg: /* External Tools Settings */

2024-09-30T15:05:17Z

External Tools Settings

← Nächstältere Version		Version vom 30. September 2024, 15:05 Uhr
Zeile 1:		Zeile 1:
	== External Tools Settings ==		== External Tools Settings ==
			[[Installing_additional_Frameworks/en\|Installing Additional Frameworks]]


	----		----

Cg: /* External Tools Settings */

2024-06-28T10:28:08Z

External Tools Settings

← Nächstältere Version		Version vom 28. Juni 2024, 10:28 Uhr
Zeile 1:		Zeile 1:
	== External Tools Settings ==		== External Tools Settings ==
	&~~bbsp~~;
	----		----

Cg: /* External Tools Settings */

2024-06-28T10:17:30Z

External Tools Settings

← Nächstältere Version		Version vom 28. Juni 2024, 10:17 Uhr
Zeile 1:		Zeile 1:
	== External Tools Settings ==		== External Tools Settings ==
			&bbsp;
			----

			[[Settings/en\|Back to the main page "Settings"]]
			[[Category:Settings]]

Cg: Der Seiteninhalt wurde durch einen anderen Text ersetzt: „== External Tools Settings ==“

2024-06-28T10:16:51Z

Der Seiteninhalt wurde durch einen anderen Text ersetzt: „== External Tools Settings ==“

← Nächstältere Version		Version vom 28. Juni 2024, 10:16 Uhr
Zeile 1:		Zeile 1:
	~~===~~== ~~Python2~~ ~~and Python3~~ Settings ~~===~~==		== External Tools Settings ==
	Be aware that there exist two partially incompatible python versions (2.x and 3.x) and there exist packages
	which are compatible with both and also packages which need a particular version.
	Although Python2.x is about to be obsoleted now, there are still older packages/applications around,
	which have not yet been ported to 3.x. Expecco deals with this situation by allowing you to specify which python interpreter to be used for your actions and also to have multiple interpreters (with different versions) running in parallel.

	You can skip this section, iff all of your python modules run in Python3.x and only specify one single path/module setup in the top area of the settings dialog (named "Python")

	Due to some bad planning in the python community, there were a number of changes between python2.x and python3.x, which may (and usually do) make scripts written for either version incompatible with the other.
	For example, the following print expression from python2:
	print "Hello World from a Python2 script\n"
	needs parentheses in python3:
	print ("Hello World from a Python2 script\n")
	and will lead to a syntax error if executed in python3.

	Although it is a good idea to use Python3 (because Python2 is going to be obsolete soon), there are many open-existing libraries for Python2 around. Thus, it may be necessary to specify an explicit interpreter version to be used for python script actions.

	If all of your actions depend on the same python interpreter version,
	it is sufficient to ensure that either the "<code>PYTHON_SHELL</code>" variable is set correctly,
	or the "Python Path" is defined in the settings to point to the correct interpreter.

	However, if you have mixed version scripts (for example, when importing python actions written by another team, which used a different version), you have to specify the python interpreter explicitly for some of the actions.

	You can either specify the version in the elementary action itself (language menu for bridged actions or #PYTHON-comment in script actions) or provide the version information dynamically without touching the action itself. The later is a bit more complicated to use, but required if you do not want to modify imported actions.

	For this, expecco contains 3 setting fields for the python interpreter: "Python Cmd Path" in the settings or "<code>PYTHON_SHELL</code>" in the shell environment, which are used when no explicit version is required, or if all of your script require the same python version, "Python2 Cmd Path" in the settings (or "<code>PYTHON2_SHELL</code>"), which are used for scripts which have been marked as explicitly requiring python2 and "Python3 Cmd Path" in the settings (or "<code>PYTHON3_SHELL</code>") for scripts which are marked to require python3.

	The python version requirements are defined in the environment of the suite/imported library in which the action is defined: a variable named "<code>PYTHON_VERSION</code>", which should be an integer with either "<code>2</code>" or "<code>3</code>" as value specifies the version to be used for ALL of the python actions within that library. Notice, that the environment of the project from which the action was imported is relevant here - not the active environment at execution time, or the suite's top environment. This version number then determines, which of the above setting is to be used (i.e. PYTHON2_SHELL/path or PYTHON3_SHELL/path).

	Using that double-indirect mechanism, it is still possible to:
	* import multiple libraries with different python-versions requirements
	* specify the paths independent of where the python interpreters are installed (i.e. the machine on which the final suite is executed may have different installation paths than the machine on which the imported libraries were developed).

	A concrete demo importing libraries which require different python interpreter versions is found in "<code>d46_Suite_using_both_Python2_and_Python3_actions.ets</code>" in the demo folder.

	Notice:<br>In expecco 19.2, you can also choose the python version in the code editor's language chooser.

Alkurz am 6. Dezember 2023 um 14:37 Uhr

2023-12-06T14:37:28Z

Änderungen zeigen

Alkurz: /* Python */

2023-12-05T15:01:07Z

Python

← Nächstältere Version		Version vom 5. Dezember 2023, 15:01 Uhr
Zeile 182:		Zeile 182:

	===== Compatible Versions =====		===== Compatible Versions =====
	Bridged python actions have been tested with versions 2.7, 3.7 to 3.10; also pypy7-3-9 (which is a 3.9Python) has been verified to work. Please let us know, if newer (or older) versions show any incompatibilites.		Bridged python actions have been tested with versions 2.7, 3.7 to 3.11; also pypy7-3-9 (which is a 3.9Python) has been verified to work. Please let us know, if newer (or older) versions show any incompatibilites.

	Be aware that Python2.x is no longer officially supported (see [https://www.python.org/doc/sunset-python-2/ "Sunsetting Python-2"]).		Be aware that Python2.x is no longer officially supported (see [https://www.python.org/doc/sunset-python-2/ "Sunsetting Python-2"]).

			=== Debugging ===

			==== With external Python bridge ====

			You can run the Python bridge outside of expecco in a development environment (e.g. PyCharm) and debug the code of the bridge, but above all the Python blocks.

			To do this, you can copy the Python bridge code to the clipboard and transfer it to the IDE (button "''Copy Bridge Code to Cipboard''").

			Exit already running Python bridges, select "''Connect to already running bridge''" and start the bridge code in debug mode in your IDE.

			The jump from the Python bridge to the code of the blocks takes place in the line
			result = actionFn(actionArgs, actionOutPins)
			To debug the code in the blocks, a breakpoint should be set here.

	== Jython and IronPython ==		== Jython and IronPython ==

Cg: /* C++ Interface */

2023-10-24T12:00:49Z

C++ Interface

← Nächstältere Version		Version vom 24. Oktober 2023, 12:00 Uhr
Zeile 255:		Zeile 255:
	When later loaded and executed, these binaries will be used and no attempt is made to compile the C-code dynamically on the target.		When later loaded and executed, these binaries will be used and no attempt is made to compile the C-code dynamically on the target.
	Use this, if no compiler toolchain is available on the target.		Use this, if no compiler toolchain is available on the target.

	==== C++ Interface ====
	C++ functions should be called indirectly via a C function wrapper (i.e. <code>extern "C"</code>).
	<br>Object references can be passed from the bridge to expecco using the "<code>makeRef</code>" wrapper function.

	== Root Cling ==		== Root Cling ==

Cg: /* C++ Interface */

2023-10-24T11:59:54Z

C++ Interface

← Nächstältere Version		Version vom 24. Oktober 2023, 11:59 Uhr
Zeile 257:		Zeile 257:

	==== C++ Interface ====		==== C++ Interface ====
	C++ functions should be called indirectly via a C function wrapper. ~~C++ objects can be passed in/out using the~~ "~~makeRef~~" ~~wrapper function.~~		C++ functions should be called indirectly via a C function wrapper (i.e. <code>extern "C"</code>).
			<br>Object references can be passed from the bridge to expecco using the "<code>makeRef</code>" wrapper function.

	== Root Cling ==		== Root Cling ==

Cg: /* Store object files in project */

2023-10-24T11:58:07Z

Store object files in project

← Nächstältere Version		Version vom 24. Oktober 2023, 11:58 Uhr
Zeile 255:		Zeile 255:
	When later loaded and executed, these binaries will be used and no attempt is made to compile the C-code dynamically on the target.		When later loaded and executed, these binaries will be used and no attempt is made to compile the C-code dynamically on the target.
	Use this, if no compiler toolchain is available on the target.		Use this, if no compiler toolchain is available on the target.

			==== C++ Interface ====
			C++ functions should be called indirectly via a C function wrapper. C++ objects can be passed in/out using the "makeRef" wrapper function.

	== Root Cling ==		== Root Cling ==

Cg: /* Environment Variables */

2023-10-24T11:56:23Z

Environment Variables

← Nächstältere Version		Version vom 24. Oktober 2023, 11:56 Uhr
Zeile 64:		Zeile 64:
	Notice, that additional values provided at a script action's input pin will take precedence over what is defined in these global settings.		Notice, that additional values provided at a script action's input pin will take precedence over what is defined in these global settings.

	A common variable to export is "<code>LD_LIBRARY_PATH</code>", which might be needed by the CBridge (see below).		A common variable to export is "<code>LD_LIBRARY_PATH</code>", which might be needed by the [[#CBridge \| CBridge]] (see below).

	== Shell (Win32 only) ==		== Shell (Win32 only) ==