-
Notifications
You must be signed in to change notification settings - Fork 199
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
Remove support for Python 3.8 and 3.9 #986
Comments
I'm still using Python 3.6 via the SLURM extension to Benchexec (#995), on the Komondor cluster in Hungary. Komondor by default has Python 3.6.8 installed. Because right now benchexec works for me using this python version, I don't want it to break -- I do understand that other parts of Benchexec may already rely on later versions, and also that this could be modified any time, but right now, it still works just fine. However, should Benchexec move away from supporting (even unofficially) this version, the worst that could happen for me is that I would need a local copy of a newer python version, which I don't think is that hard to achieve - however, I admit I have not yet tried to go down that route. So I don't want to be the one holding back benchexec with my (admittedly very niche) use-case. |
Thanks for the feedback. Then we will follow the current plan. |
I think let it be as it is for now. Benchexe should remove support for Python 3.8 once Ubuntu 20.04 goes out of support, in 2025. And jumping directly to 3.10 version of python will be a great decision. |
Since version 69.3.0 the names of the produced build artifacts changes, but we prefer to keep the old names for compatibility.
BenchExec 3.22 was just released and will be the last version supporting Python 3.7. |
As announced in the changelog of BenchExec 3.22 and on the issue tracker. Part of #986.
For the record: Python 3.10 would finally allow us to implement #433 (comment), so the current plan is to indeed start requiring Python 3.10 for BenchExec in 2025. |
As announced in the changelog of BenchExec 3.22 and on the issue tracker. Part of sosy-lab#986.
As discussed previously we will remove support for Python 3.7 in one of the next releases. I suspect this will not be critical because all currently supported versions of Ubuntu or Debian ship Python 3.8 or newer. We should still wait for at least one more release and announce the upcoming change in the changelog.
As a heads-up, we plan to remove support for Python 3.8 once Ubuntu 20.04 goes out of support, i.e., in April 2025. At that point we might even drop support for Python 3.9 and jump directly to requiring Python 3.10.
Please comment here if either of these plans are problematic for you.
The text was updated successfully, but these errors were encountered: