Hi again Pino! On Fri, Jul 03, 2020 at 06:19:29PM +0300, Dmitry Shachnev wrote: > Hi Pino! > > On Thu, Jul 02, 2020 at 01:37:54PM +0200, Pino Toscano wrote: > > [...] > > > > In any case, I don't have much experience with sip & PyQt. If you have > > some time to investigate it, and possibly send a merge request upstream > > (see https://invent.kde.org/graphics/krita), that'd be awesome. > > Working on it. Hopefully I will have it ready in a couple of days. I have an update on PyQt5 vs. SIP 5 status. Unfortunately, things got a bit more complicated recently. Upstream is going to release SIP 6 in the beginning of next year, which will be not co-installable together with SIP 5, and which will not have /usr/bin/sip5 “legacy” script: https://www.riverbankcomputing.com/pipermail/pyqt/2020-September/043201.html https://www.riverbankcomputing.com/pipermail/pyqt/2020-September/043162.html sip5 was a script to ease upgrades from SIP 4, and it has a set of options similar to SIP 4's /usr/bin/sip. Upstream now recommends using their new tools, sip-build and similar ones. See the documentation: https://www.riverbankcomputing.com/static/Docs/sip/ This means that next year we will have SIP 4 and SIP 6 in Debian, but not SIP 5. My upstream work on Krita made use of /usr/bin/sip5, so it will need to be ported to the new tools in order to support SIP 6 (and PyQt6). At the same time, upstream says that it will remain possible to compile applications with SIP 4 even when PyQt5 uses newer SIP. So now I think the best plan is: - Please keep using SIP 4 for Krita for now. - Please test that it still works fine with PyQt5 in experimental. - Ask upstream to migrate to the new tools to be prepared for SIP 6 / PyQt6. -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature