<div class="gmail_quote">On Wed, Aug 26, 2009 at 5:32 PM, Matt McCormick <span dir="ltr"><<a href="mailto:matt@mmmccormick.com">matt@mmmccormick.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Andreas Pakulat <apaku@...> writes:<br>
> On 19.08.09 08:34:26, Philip Lowman wrote:<br>
> > Speaking of the existing FindPython* scripts they do not support v3.0 yet.<br>
> > Is there a need to maintain support for picking 2.x if two versions of<br>
> > python are installed?<br>
><br>
> As Py2 and Py3 are basically incompatible IMHO A separate FindPython3 would<br>
> be better than letting the module try to "guess" py2 vs. py3 if both are<br>
> installed. The project using Python should have decide on wether it works<br>
> with Py3 or not.<br>
><br>
<br>
</div>Python 2.X are also incompatible with each other sometimes, and a user can have<br>
multiple 2.X and 3.X installed. IMHO, having different modules for every<br>
version is not the write way to go. Just make it a configuration variable in<br>
FindPythonLibs.cmake</blockquote><div><br>I agree with either approach, but don't have the time to work on the modules. :(<br><br></div></div>-- <br>Philip Lowman<br>