Just to clarify,
Do $System.Python.Debugging(1)
Will end up causing the C piece of SW that translates IRIS to python to call this:
void PyErr_PrintEx(int set_sys_last_vars)If set_sys_last_vars is nonzero, the variable sys.last_exc is set to the printed exception.In practice what this means, is somewhere close to your exception this gets called:
if (PyErr_Occurred()) PyErr_Print();
Which means you will actually be able to do a useful pdb post mortempdb.pm() or USER>d pdb.pm()After your exception.
If you want to stay on 23.1, can you use RH9 or ubuntu22 iris kit? It wont be quite 3.11, but at least it wont be 3.6!
If you are saying that you took a RH8 server and made python3 symbolic link point to a poorly supported development stream of 3.9->3.10->3.11->3.12 I would be very worried if your server was actually going to stay up. Its OK to install a "python3.11" link for experimentation but its not exactly supported like 3.6 would be on RH8.
In general you want to stay with something the OS vendor supports, and this is the way IRIS works as well. IRIS doesn't want to be in the business of telling customers to install a non default python version. IRIS doesn't ship python on UNIX and the quality group will focus the vast majority of its efforts on testing the default python of the OS.
If you must stay on RH8, you can try 24.1 and Flexible... but you would still need a support plan that lasts through deployment. Its not good to rely on a dev stream.
BTW the main iris integration is not with the python3 binary. Its with something called libpython.so, which is an optional component of python. That's what "embedded" means.
--
Philip
Anything that's in python sys.modules (plenty of other examples) isn't likely to work very well because of the way the namespaces are merged.