-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Python][Packaging] Drop Python 3.8 support #43518
Comments
I am going to start working on this as we are one month away to the deprecation date. |
I've just realised while creating the PR that the end of support is end of October. When we dropped support for 3.7 on our October release the Python version had already been deprecated on June, see: https://endoflife.date/python |
Personally I don't think we need to do that for those two(?) weeks that Python 3.8 will still be officially supported when Arrow 18.0 is expected to be out. And anyway, it's also not because Python 3.8 is EOL at the end of October that everyone will at once stop using it, so it is still a trade-off decision we have to make how long we want to support Python 3.8. |
### Rationale for this change Python 3.8 is End of Support on 31st October 2023. We can drop support for pyarrow 18.0.0. See: https://endoflife.date/python ### What changes are included in this PR? Remove support for 3.8. Update minimum required Python version and update some CI jobs to use the minimum Python supported version ### Are these changes tested? They will be tested via Archery ### Are there any user-facing changes? Yes in terms of not supporting older versions of Python. This will be a breaking change for some users but not for the API itself * GitHub Issue: #43518 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
Issue resolved by pull request 43970 |
Previous issue for Python 3.7: #34788
We dropped Python 3.7 support in pyarrow 13.0 (August 2023). If we follow the same pattern, we should be able to drop 3.8 support for pyarrow 18, since by the time of that release it should have reached end of life (2024-10, https://devguide.python.org/versions)
The text was updated successfully, but these errors were encountered: