Oct-13-2017, 02:52 PM
So to be more clear about what I'm facing, let's say we have A.dll, which was written by some other team, which links with python2.7/libs/python27.lib, and calls Py_Initialize. I'm writing B.dll, which links with python3.x/libs/python3x.lib and calls Py_Initialize. Is anything bad going to happen here if the application runs the code from both A.dll and B.dll, in one order or the other?
I'm not talking about the scripts - scripts written by the A team will be designed for 2.7 and will run in the 2.7 interpreter, and scripts my team writes will be designed for 3.x and will run in the 3.x interpreter. The python modules will be completely separate and the paths will be set up to keep things straight.
By sub-interpreter, I mean using Py_NewInterpreter, so if B.dll and C.dll are both using python 3, they will each obtain a separate interpreter environment.
Thanks!
I'm not talking about the scripts - scripts written by the A team will be designed for 2.7 and will run in the 2.7 interpreter, and scripts my team writes will be designed for 3.x and will run in the 3.x interpreter. The python modules will be completely separate and the paths will be set up to keep things straight.
By sub-interpreter, I mean using Py_NewInterpreter, so if B.dll and C.dll are both using python 3, they will each obtain a separate interpreter environment.
Thanks!