Sorry about the surprise. To get the python 3 bindings into the stable
release, we needed to use a newer version of boost. The quickest way to
do that leverages boost169 from EPEL. It was not possible to involve 2
different boost versions in a single build. So to use python2-condor or
python3-condor, you have the run-time dependency on boost169-python2 or
boost169-python3. I tried linking the boost libraries statically to
avoid this dependency. However, one cannot link the static boost
libraries into the dynamic python htcondor and classad libraries.
On RHEL7 and derivatives, boost169-python2 or boost169-python3 are
required to use the HTCondor python bindings.