Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Python][Packaging] Drop Python 3.8 support #43518

Closed
jorisvandenbossche opened this issue Aug 1, 2024 · 4 comments
Closed

[Python][Packaging] Drop Python 3.8 support #43518

jorisvandenbossche opened this issue Aug 1, 2024 · 4 comments
Assignees
@raulcd
Labels
Component: Packaging Component: Python
Milestone
18.0.0

Comments

@jorisvandenbossche
Copy link
Member

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)
@jorisvandenbossche jorisvandenbossche added this to the 18.0.0 milestone Aug 22, 2024
@raulcd
Copy link
Member

raulcd commented Sep 4, 2024

I am going to start working on this as we are one month away to the deprecation date.

@raulcd raulcd self-assigned this Sep 4, 2024
raulcd added a commit to raulcd/arrow that referenced this issue Sep 5, 2024
@raulcd
apacheGH-43518: [Python][Packaging][CI] Drop Python 3.8 support
03fbc60
@github-actions github-actions bot mentioned this issue Sep 5, 2024
Merged
@raulcd
Copy link
Member

raulcd commented Sep 5, 2024

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
Should we hold this to 19.0.0?

@jorisvandenbossche
Copy link
Member Author

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.
But personally, I think we can certainly stop providing wheels for Python 3.8 around the time of the EOL (people can always still install the previous version of pyarrow, or even building from source will probably still work), and providing wheels for 5 Python versions (3.9-3.13) seems sufficient.

raulcd added a commit to raulcd/arrow that referenced this issue Sep 16, 2024
@raulcd
apacheGH-43518: [Python][Packaging][CI] Drop Python 3.8 support
929d4e0
jorisvandenbossche pushed a commit that referenced this issue Sep 16, 2024
@raulcd
GH-43518: [Python][Packaging][CI] Drop Python 3.8 support (#43970)
aa6ab95 
### 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 <raulcumplido@gmail.com>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
@jorisvandenbossche
Copy link
Member Author

Issue resolved by pull request 43970
#43970

@raulcd raulcd mentioned this issue Sep 19, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raulcd raulcd

Labels
Component: Packaging Component: Python
Projects
None yet
Milestone
18.0.0
Development

No branches or pull requests
2 participants
@raulcd @jorisvandenbossche