-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lost compatibility with Python2 #207
Comments
I thought we had decided that at one of the meetings after #182 was merged, because with that we removed the last CI workflows that were still using python2. At least I stopped worrying about python2 compatibility after that, and also some of the things that are in #143 would break, e.g. |
Noted here: https://codimd.web.cern.ch/lkFym47kSdKGWqmPLCpf-w#Podio7 python3 only |
thanks. Seems I forgot about that. I will update some of the docs |
It seems PODIO lost its compatibility with Python2 by introducing formatted strings in e.g.
podio/python/generator_utils.py
Line 120 in eb298b1
Are we ready to give up on Python2 compatibility?
At the same time, the handling of Python2 vs Python3 is not really stable for systems, where Python 3 is explicitly called python3. And Python2 just called python, Throughout the CMake macros we just talk about python
The text was updated successfully, but these errors were encountered: