Re: [HTCondor-devel] Python3 HTCondor bindings

[nathan.panike@xxxxxxxxx]

This is in gittrac at #3543 and #3555.

https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=3555
https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=3543

> Hi,
> 
> Could someone stage an external for boost 1.54?  Jaime?
> 
> Right now, the boost external is in a curious state - it seems all =
> platforms use 1.49 except for recent Windows, which uses 1.54 (and no =
> external is staged for 1.54).  Unfortunately, boost 1.49 does not =
> support python3.
> 
> Once we switch boost versions, I believe we have a working set of =
> bindings for python3 (they pass unit tests for proper builds).
> 
> Also, I discovered why on Fedora 19 python3 is used even though on the =
> other Fedoras, python2 is used.  =46rom the NMI glue:
> 
> if($platform =3D~ /Fedora1[78]$/) {
>         $defines{python_version} =3D =
> "-DPythonLibs_FIND_VERSION:STRING=3D2.7";
> }
> 
> Well, that's easy enough to fix!
> 
> Given working python3 bindings, there's still more CMake surgery to =
> perform.  I think we ought to build up to three sets of python bindings, =
> depending on what versions are present:
> 
> - Python 2.6
> - System python
> - Python 3
> 
> This would cover the use cases of RHEL5 (python2.4 is system default but =
> installing python2.6 is a popular choice) and Fedora (python 2.7 and 3.x =
> are installed by default).  I admit I might wuss out and only do one =
> python2 and one python3 build -- for a UW-style build, boost.python =
> needs to be rebuilt for each and I'm not feeling that generous toward =
> RHEL5.  Blech!