python 3.10 -> 3.14 support & update CI actions components#303
python 3.10 -> 3.14 support & update CI actions components#303
Conversation
|
also updated the CI actions components, that will need testing... |
|
Note that current test failure is not conclusive as it is running tests for 3.9 (because of tests declarations in the master branch) while the commit specifies py3.10+ is required... |
|
Added 3.14 coverage. On my machines, tests on 3.10 & 3.14 are ok ; only things that are not tested are the CI jobs. |
2d501e8 to
42f7fb6
Compare
* drop python 3.9 support * extend coverage to python 3.14 (and update dependencies) * update CI components
42f7fb6 to
5466b7c
Compare
| @@ -9,7 +9,7 @@ version: 2 | |||
| build: | |||
| os: ubuntu-22.04 # <- add this line | |||
There was a problem hiding this comment.
could you also update that to ubuntu-lts-latest while we're at it? this should prevent us from having to worry about it in a few years
| pandas >= 2.3.3, < 3.0 | ||
| geopandas >= 1.1.3, < 2.0 | ||
| pyarrow >= 23.0.1 | ||
| tqdm >= 4.56 | ||
| platformdirs >= 4 | ||
| unidecode >= 1.3 | ||
| urllib3 >= 2.2 | ||
| shapely >= 2 | ||
| shapely >= 2.1.2 | ||
| requests >= 2.32 | ||
| requests-ratelimiter >= 0.7 | ||
| openpyxl | ||
| openpyxl >= 3.1.5 |
There was a problem hiding this comment.
I'm wondering whether these version bumps are actually necessary: we should pin versions that are compatible with our API and not based on the Python version they support
There was a problem hiding this comment.
given the issue raised in #304 I'd just switch pandas to pandas >= 2.2.0, < 4.0 and keep the other versions unchanged
python 3.9 reached end-of-life status in october 2025