On Wednesday 26 August 2009, Matt McCormick wrote: > Andreas Pakulat <ap...@...> writes: > > On 19.08.09 08:34:26, Philip Lowman wrote: > > > Speaking of the existing FindPython* scripts they do not support v3.0 > > > yet. Is there a need to maintain support for picking 2.x if two > > > versions of python are installed? > > > > As Py2 and Py3 are basically incompatible IMHO A separate FindPython3 > > would be better than letting the module try to "guess" py2 vs. py3 if > > both are installed. The project using Python should have decide on wether > > it works with Py3 or not. > > > > Andreas > > Python 2.X are also incompatible with each other sometimes, and a user can > have multiple 2.X and 3.X installed. IMHO, having different modules for > every version is not the write way to go. Just make it a configuration > variable in FindPythonLibs.cmake
This may become messy. I agree with Andreas that having a separate module for Python3 would be better. Since they are not compatible, I don't see a reason why one module should search for both. Alex _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
