Question about using Python Plug-ins with LSB's, Docker vs. Compiled from source

I switched to using Docker many months ago. I have a Python Plug-in script that uses a number of PIP modules and have not had any issues when using Docker, and I previously compiled my own Orthanc and Plug-ins from source before I started using Docker, without any real issues.

I have a client who is having some issues using my Python script, I think because he is not using Docker and the Orthanc Python Plug-in .so that he is using does not recognize the PIP modules on the system. There is a error message in Orthanc saying … PIP module not found.

Does he need to compile the Python Plug-in from source, and is there something ‘special’ that needs to be done for the extra PIP modules to be recognized ?

I vaguely remember having to install the PIP modules as the sudo user and then linking to the ‘correct’ Python version, at least on MacOS. He is using one of the more recent versions of UBUNTU.

Any suggestions or pointers welcome.

Stephen D. Scotti

Depends on environment he is using. If docker then he need to repackage the original image with essential python module

After a little more investigation it looks like my friend is using a LSB .so that is an older version configured to use Python 3.9, whereas his system has 3.10.4 installed.

The LSB’s available look like they have this as the latest ?

≈/plugin-python/debian-bullseye-python-3.9/mainline/

Just wondering if there is a version built for 3.10, or if I should just probably build the .so from source ?

I take it that apt install orthanc-python will be an older version, and that the LSB’s and Debian packages are a little bit behind ?

Stephen D. Scotti, M.D.