-
-
Notifications
You must be signed in to change notification settings - Fork 70
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 Python 3.8 support, add 3.13 #572
Conversation
Wait a bit until actions/setup-python publishes official 3.13 packages. |
@nicoddemus looks like this dropped off your radar? Looking at #107 the CI seems pretty broken currently. |
e2b7f47
to
00b49f1
Compare
Thanks for the ping, indeed I had completely forgotten about this one. Rebased, let's see. |
I don't think PySide2 is still supported, the last release was in 2022, and of course there is no more releases for more recent Python versions. Perhaps we should drop official support for it as well? |
0eb4bcb
to
24e73dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for picking things up again, looks great!
I suppose we could, though not sure how much there is to gain if we still keep Qt5 (via PyQt5) around? https://pypi.org/project/PyQt5/#history seems alive enough to keep it IMHO. |
The latest release seems to have changed the message: ``` ValueError: Error calling Python override of QObject::event(): mistakes were made' ```
Not available yet on Python 3.13 on all platforms. Not available on MacOS.
24e73dc
to
28223c0
Compare
I personally have interest in keeping PyQt5 compatibility because that's what we still use at ESSS, plus it is still maintained as you said. I will open a PR removing pyside2 and we can evaluate if it is worth it or not. |
No description provided.