On 06/29/2015 09:41 PM, Mark Moll wrote:
I have attached an alternative module that replaces the two current
modules for finding python-related info. With the current modules
it is easy to end up in a situation where the interpreter’s version
and the library version do not match, which
Brad,
Thanks for the detailed explanation. I figured there were use cases not handled
by my module. For instance, I hadn’t thought of cross-compilation. Since in my
own project these unhandled cases haven't come up, I’ll stick with own module
for now.
With the existing modules it might be
I just want to add that I also saw a colleague running in the issue
described in the beginning of the thread and that the version reported by
the Python module and the PythonLibs one were different strings, even
though the version was actually the same. It happened on latest Debian I
think.
How I
