RHEL 9.8 python bindings for python 3.12

[Andres Ayala]

Hi,

I am planning an activity to migrate our facilities from RHEL 9.8 to RHEL 10.2 that implies replacing python 3.9 with python 3.12.

RHEL 9.8 has official support for python 3.12 (can be installed as part of the base OS), so the safest way is to migrate first to python 3.12 and then change the OS.

However, for the condor bindings my only options are to use the pypi package (but it bundles its own copy of the condor libraries) or to repackage myself the "python3-condor" with each condor release.

The best option would be to have the rpm "python3.12-condor" in the official yum repository (https://htcss-downloads.chtc.wisc.edu/repo/25.x/el9/x86_64/release/)

Are you planning to add that rpm to the releases? Or it is better that I follow one of the other approaches...

Regards!

 

Andrés Ayala

EUMETSAT Data Processing System Engineer

Any email message from EUMETSAT is sent in good faith but shall neither be binding nor construed as constituting a commitment by EUMETSAT, except where provided for in a written agreement or contract or if explicitly stated in the email. Please note that any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of EUMETSAT. This message and any attachments are intended for the sole use of the addressee(s) and may contain confidential and privileged information. Any unauthorised use, disclosure, dissemination or distribution (in whole or in part) of its contents is not permitted. If you received this message in error, please notify the sender and delete it from your system.

[Stefano Belforte]

I think that a feature of new python binding is that they largely independent of
python version. I.e. you should be able to update python to 3.12 in a RHEL 9.8
machine and verify that it works.

Stefano

[Andres Ayala]

Yes, the python-condor is pure python code,

The problem is that it deploys correctly the python modules under:

/usr/lib64/python3.9/site-packages

But the python 3.12 expects the modules in:

/usr/lib64/python3.12/site-packages

And if I choose the path of the pypi package it comes with its own libraries (classad2/classad2_impl.abi3.so, htcondor.libs/libSciTokens-ee37b48c.so.0.0.2, ...) something that raises questions in the reviews.

I know the problem is not difficult to solve, but the best thing would be that it is possible to do:

> dnf install -y condor python3.12-condor

And then be sure that python3.12 is going to use exactly the libraries installed by condor.

Currently I am repackaging python3-condor for python 3.12 (it is easy, the new bindings are really nice).

I was asking because I suspect I am not the only one that will need to do the migration 🙂

Thanks!

Andrés Ayala

---

De: Stefano Belforte <stefano....@cern.ch>
Enviado: miércoles, 22 de julio de 2026 15:42
Para: Andres Ayala <Andres...@eumetsat.int>; htcondo...@g-groups.wisc.edu <htcondo...@g-groups.wisc.edu>
Cc: stefano....@cern.ch <stefano....@cern.ch>
Asunto: Re: [HTCondor-users] RHEL 9.8 python bindings for python 3.12

 

WARNING: This email originated outside the organisation. Treat links and attachments with caution.

[Tim Theisen]

Hello Andres,

Our current bindings use the Python Limited C API which works with Python 3.3 to 3.14. We do need to do a little more work to package the bindings to  reflect this version independence.

Using the PyPI versions of the bindings is a good alternative. I would not worry about the bundled libraries. The Python bindings use the same wire communication protocol regardless of which libraries are in use.

We do not plan to make a special RPM version for every Python version.

...Tim

Any email message from EUMETSAT is sent in good faith but shall neither be binding nor construed as constituting a commitment by EUMETSAT, except where provided for in a written agreement or contract or if explicitly stated in the email. Please note that any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of EUMETSAT. This message and any attachments are intended for the sole use of the addressee(s) and may contain confidential and privileged information. Any unauthorised use, disclosure, dissemination or distribution (in whole or in part) of its contents is not permitted. If you received this message in error, please notify the sender and delete it from your system. --
Archives for older messages are found at https://www-auth.cs.wisc.edu/lists/htcondor-users/
---
You received this message because you are subscribed to the Google Groups "HTCondor Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to htcondor-user...@g-groups.wisc.edu.
To view this discussion visit https://groups.google.com/a/g-groups.wisc.edu/d/msgid/htcondor-users/BE1P281MB243545655F868F516D82A72FF8C12%40BE1P281MB2435.DEUP281.PROD.OUTLOOK.COM.

-- 
Tim Theisen (he, him, his)
Release Manager
Center for High Throughput Computing
University of Wisconsin - Madison
3695 Morgridge Hall
1205 University Ave
Madison, WI 53706