https://bugs.kde.org/show_bug.cgi?id=391748

--- Comment #4 from Alexander Schlarb <alexander-kde@ninetailed.ninja> ---
> I've thought about doing something about it but I don't think it's worth the 
> effort at this point, especially considering how there's both PySide (Qt for 
> Python now) and PyQt5.

Could you explain the difference between PySide and PyQt5 and why I've never
seen a Python Qt application using the former (although it supposedly is the
“official” binding)?

> It would surely be possible to have an extra org.kde.python.Platform kind of 
> thing. Or an extension should be possible as well, haven't explored this 
> approach, it would be welcome if someone did.

A separate platform would be overkill, but a runtime extension could be decent
compromise there. Although I was secretly hoping to have it in the main
platform image, as Python support in FDO/GNOME runtimes is available OOTB and
as a Python programmer I of course love that. :-P

> The biggest problem with basing the platform is that we'd have to choose 
> against Qt WebKit and Qt WebEngine, which is another crazy place that adds 
> complexity.

I'm sorry, I don't understand what you mean with “basing” here?
QtWebEngine/QtWebKit are not part of this and at least PyQt5 allows building
the Python binding for QtWebEngine separately.

(OT: Regarding that, I had been privately wondering if wouldn't make sense to
have these as runtime extensions [with their respective Python bindings].)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to