Python bindings for my custom model
-
If you name your module based on the SAMSON Element UUID, as suggested in the sample, then you can import it as follows:
import SE_F2078F9E_F2CB_BA72_EE86_1E01A10B63D4 as pybindtutorialWarning: if your SAMSON Element has a python bindings in it, meaning it is linked to a python library, then for users to use this Element they will need to have Python installed, which should be the case if they already use Python Scripting.
-
Hi, I have tried to get it working but Python Scripting has stopped working for me (I think it might be due to changes in my python installation since I first installed it). I'm using Anaconda3, I reinstalled everything with Python 3.7, but was unable to see the Python Scripting module loaded. After a downgrade to python 3.6 I can see the module loaded but not the jupyter qtconsole on it (if I run jupyter qtconsole from conda it runs fine, the versions it displays are: Jupyter QtConsole 4.4.2 and Python 3.6.7)
I followed the instructions of the documentation but was unable to make it run, maybe I'm missing something?
Thank you and best regards,
Elisa
-
Dear @Elisa
Thank you for reporting it! I will add the tested installations to the installation tutorial.
I have not tested Python Scripting with python 3.7. I do not expect it to work with python 3.7 since it was compiled against python 3.6 and is linked to python3.6 library.
The loaded python scripting means that you probably have a proper version of python library. The fact that Jupyter QtConsole is not loaded might mean that its version is not the one against which it was compiled.What OS do you use?
I am using Python Scripting in Linux with Python 3.6.4 and Jupyter QtConsole 4.3.1 from Anaconda 5.1 installation. Anaconda 5.2 installation might also be fine (tested only on Windows).
-
I have added a list of tested installation: https://documentation.samson-connect.net/scripting-guide/python-script-installation/
-
Is it possible for you to try to downgrade Jupyter QtConsole to v.4.3.1 and check?
-
Hi, I'm using Anaconda 5.3.1 I just downgraded to QtConsole 4.3.1 and python from 3.6.7 to 3.6.5, but I still don't get the jupyter qtconsole on Python Scripting module. The versions I'm using for the rest of dependencies are:
jupyter 1.0.0
jupyter_client 5.2.3
jupyter_console 6.0.0
jupyter_core 4.4.0
numpy 1.15.4I will try downloading Anaconda 5.2 and reinstalling from there.
-
Sorry for this issue!
It is really due to linking to particular versions of libraries we do in Python Scripting.I will try to reproduce your case and come up with a full list of dependencies and proper versions for required packages.
In my Anaconda installation on Linux these packages have the following version:jupyter 1.0.0 jupyter_client 5.2.2 jupyter_console 5.2.0 jupyter_core 4.4.0 numpy 1.14On Windows:
jupyter 1.0.0 jupyter_client 5.2.3 jupyter_console 5.2.0 jupyter_core 4.4.0 numpy 1.14.3Could you, please, try downgrading numpy to v.1.14?
If it won't work, it would be nice if you will be able to try the Anaconda3 installation written in the Tested installations section in the documentation.
-
I have run conda install anaconda=5.2, now all the packages match the versions you have, but I still am unable to see the the jupyter qtconsole on the Python Scripting module. Maybe the error is somewhere else, is there a log a could check?
-
What OS do you use?
Could you, please, check the environment variables for which Python paths are set there? -
Yes, I'm using Windows 10, and the Path variables for anaconda3 are set (I added them when installing). I will try to install Anaconda3 for all users, in case the problem comes from this.
-
It should not be a problem, it should work for a user installation. On my Windows 10 I have it installed only for my user.
-
To see the SAMSON log on Windows, you can open a terminal (Power Shell) and launch SAMSON from there (provide the full path to the SAMSON executable or launch from where it is installed):
.\SAMSON-Core.exe --logfile="samson.log"Then you can open the log file and search for the line: "Python Scripting: initialization ..."
Could you, please, post here what you have in this log after this line (related to the Python Scripting). -
By the way, which version of Anaconda3 you installed now, the 64-bit one? Anaconda3-5.2.0-Windows-x86_64.exe (see https://repo.anaconda.com/archive/)?
-
Yes, I installed the 64bit.
I think the problem is that I might not have set the appropriate paths. If I execute jupyter qtconsole from within anaconda, it runs fine. But if I try to execute it from the command line, it throws an error saying it can't find PyQt5. I also realized that they added the folder Library/usr/bin to the PATH variable, but in my anaconda installation there is no such folder. I think maybe I'm missing a path.
-
Sorry, I just saw the logging option! I went back to a clean installation of Anaconda3 with python 3.7 to see if I could load by default the jupyter qtconsole from cmd. So now the error is:
=================================================================== "7B654CE6-E38C-B97F-6746-4FD6934487C2.dll" Errors ------------------------------------------------------------------- > "Cannot load library" "Sorry I cannot help you" =================================================================== =================================================================== 7B654CE6-E38C-B97F-6746-4FD6934487C2.dll Errors ------------------------------------------------------------------ > Cannot load library Sorry I cannot help you -
@Elisa
This error means that it was not possible to load the module, in the case of the Python Scripting Element it is probably due to the wrong python library version (since Python Scripting is compiled and linked against python3.6 library). -
If you have installed Anaconda3 you have PyQt5 installed. Apparently, the error when you launch Jupyter QtConsole from the command line and it cannot find PyQt5 is due to a conflict with your Qt installation (e.g. Qt 5.9.3) either because of the order in the PATH environment variable or, if you were changing versions of packages in your anaconda installation, because of the not suitable version of PyQt5 for jupyter qtconsole (but then it would not allow launching it from within the anaconda).
Could you, please, check the PATH environment variables (the system one and the user one).
-
This is how the user Path environment variable looks like for my installation on Win10:
-
I checked the path environment, but it looks like yours, I also have there Qt\5.8\msvc2015_64\bin and Qt\5.8\msvc2015_64\lib (makes no difference if I add them or remove them). I must have broken the Python installation at some point, I also think the problem is on my side, probably regarding the paths. I will keep looking!
-
Sorry again for the issue!
The Python Scripting Element is quite dependent on particular version of python and might be on versions of some packages (e.g., jupyter qtconsole) as well.If you think that it is due to your broken Anaconda3 installation, I would advice you to uninstall all the anaconda installations (check the Path environment variables as well), restart your PC and install the Anaconda3-5.2.0-Windows-x86_64.exe (https://repo.anaconda.com/archive/Anaconda3-5.2.0-Windows-x86_64.exe).
