Remove support for py38 and py39 #50
Conversation
pyproject.toml
Outdated
| "qtconsole>=4.3,!=5.4.2", | ||
| "pvextractor>=0.2", | ||
| "importlib_resources>=1.3; python_version<'3.9'", | ||
| "importlib_resources>=1.3; python_version<'3.10'", |
There was a problem hiding this comment.
| "importlib_resources>=1.3; python_version<'3.10'", |
no longer needed at all :D
CyclingNinja
force-pushed
the
py_ver_update
branch
from
1acb995 to
9b70122
Compare
CyclingNinja
force-pushed
the
py_ver_update
branch
from
4825701 to
f7f0e23
Compare
.github/workflows/ci_workflows.yml
Outdated
| - linux: py311-test-pyqt66-all | ||
| - linux: py311-test-pyqt514 | ||
| - linux: py311-test-pyqt515-lts-all | ||
| - linux: py314-test-pyqt68 |
There was a problem hiding this comment.
| - linux: py314-test-pyqt68 | |
| - linux: py314-test-pyqt68-dev |
Let's try with this one – we haven't actually set up any packages' dev versions (maybe we should?), but this will set the PIP_EXTRA_INDEX_URL needed to find shapely downloads – I'm a bit surprised that building h5py succeeded here; for glue-core at least I found both failed.
There was a problem hiding this comment.
Should not push these from my phone somewhere in a waiting room... Completely missed the developer versions section below, as well as its glue-core etc. deps! So that should be moved down there of course.
There was a problem hiding this comment.
The test envs are looking fine now once they are organised properly ;-)
There still is a commit merging main into this branch that I don't understand, but the PR looks mergeable.
Just remains to remove pixel_selection_mode.py with its fallback option to complete the transition to 1.23.
Co-authored-by: Derek Homeier <[email protected]>
CyclingNinja
force-pushed
the
py_ver_update
branch
from
7b24caf to
547449e
Compare
| - linux: py311-test-pyqt66-all | ||
| - linux: py311-test-pyqt514 | ||
| - linux: py311-test-pyqt515-lts-all | ||
| - linux: py314-test-pyqt68-dev |
There was a problem hiding this comment.
move to # Test against latest developer versions... below
| # Documentation build | ||
| - linux: py38-docs-pyqt514 | ||
| - linux: py313-docs-pyqt514 |
There was a problem hiding this comment.
Will probably run with py311 at most, but I'm not sure why we absolutely need docs built with PyQt5, and if they couldn't be 5.15 at least. Check with @astrofrog
| # Test a few configurations on macOS 13 (Intel, default for py<310) and 14 (Arm) | ||
| - macos: py38-test-pyqt514-all | ||
| - macos: py310-test-pyqt514-all |
There was a problem hiding this comment.
| - macos: py310-test-pyqt514-all | |
| - macos: py310-test-pyqt515-all |
5.14 should still be available with macos-13 (there are wheels for x86_64), but since those runners are going to be retired anytime from 2-12 weeks from now, no point in switching.
5.15 wheels would seem to work for all supported Pythons on arm64.
Co-authored-by: Derek Homeier <[email protected]>
2 participants
No description provided.