[vtk-developers] Do we really need the VTK version of FindPythonLibs.cmake?

[Ben Boeckel]

On Wed, Mar 18, 2015 at 23:10:21 -0600, David Gobbi wrote:
> You ask questions that are difficult to answer.  I'll spend some time going
> over the code and reminding myself of why things are the way they are,
> but I won't have a full reply for you before the weekend.

VTK's FindPythonLibs *removes* variables which are merely deprecated
upstream. That will need to be re-added when pushing upstream for
backwards-compat.

> 1) The very fact that FindPythonLibs.cmake and FindPythonInterp.cmake are
> two independent scripts has been a source of trouble (it make
> synchronization
> between the library and the interpreter difficult).  So if there are going
> to be
> substantial changes, I'd rather make a new script "FindPython.cmake" and see
> if the cmake folks are willing to adopt it.

Please make this a "FindPython2.cmake". Wanting Python2 and finding
Python3 is never acceptable (and vice versa). There are also reasonable
cases where finding both is wanted and having a single Find module
really gets in the way of that.

--Ben