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.

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

Drop support for Python 3.7 and 3.8 #1333

Closed
sgillies opened this issue Feb 29, 2024 · 5 comments · Fixed by #1334
Closed

Drop support for Python 3.7 and 3.8 #1333

sgillies opened this issue Feb 29, 2024 · 5 comments · Fixed by #1334
Assignees
Milestone

Comments

@sgillies
Copy link
Member

Numpy 1/2 compatibility will require Python 3.9. We will make that the minimum version for Fiona 1.10 as it will be for Rasterio 1.4.

@sgillies sgillies added this to the 1.10 milestone Feb 29, 2024
@sgillies sgillies self-assigned this Feb 29, 2024
@mwtoews
Copy link
Member

mwtoews commented Feb 29, 2024

Python 3.7 reached EOL in 2023 (PEP 537), so yes, it's time to go.
Python 3.8 will reach EOL in Oct 2024 (PEP 569), so is on the way out. (And related to that, I hope we may expect Fiona 1.10 sometime this year?)

@sgillies
Copy link
Member Author

sgillies commented Mar 1, 2024

@mwtoews I'm going to tag and build 1.10a1 this weekend.

@jorisvandenbossche
Copy link
Member

Numpy 1/2 compatibility will require Python 3.9.

I am not fully sure that is the case. At least in shapely, we still support Python 3.8 at the moment, and for example build wheels with numpy 2.0 that are compatible with both numpy 1.x and 2.0 and that still work for Python 3.8

Now, that said, if the release is targetted for later this year, I think it's also perfectly fine to drop Python 3.8 support, but regardless of numpy requiring it.

@jorisvandenbossche
Copy link
Member

I added some comments on #1331 related to this

@sgillies
Copy link
Member Author

sgillies commented Mar 3, 2024

@jorisvandenbossche thank you! I've added some tickets to follow up on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants