My original response was rejected by because the
domain Qt uses for mailing lists is blacklisted.

Re-sending it again with a couple of different links (to the mailing list
only, as the CCed people already got it)…

Hi Florian,

On Mon, Jan 25, 2016 at 08:12:02AM +0100, Florian Bruhin wrote:
> I'd like to discuss the future of Qt5's QtWebKit (and PyQt's bindings
> for it) in Debian. Looking at the Qt 5.6 beta, it seems like Qt
> upstream will definitely remove QtWebKit - not only from the binary
> releases, but from source releases as well.

As I have just said on another mailing list, I heard that the source
releases will be kept (at least for 5.6.x):

> As it's likely many packages will still need a Qt5 QtWebKit, and based
> on [1] ("Qt5's WebKit is expected to stay supported until Qt6") it
> looks like Debian will still continue to support it, if necessary
> building from upstream's git[2]?

Yes, we are going to continue support for QtWebKit (5.x).

> As for the PyQt5 wrappers for QtWebKit, upstream says[3]:
>     > AIUI, they are still providing source releases.  You're going to
>     > continue to support that, right?
>     Yes, if they are part of the official release. If not then I won't
>     do anything to break things, but they won't be officially
>     supported.

As one of my packages (retext) uses PyQt5's WebKit module, I won't drop it
and do my best to make sure they work.

We are even recommending it as a replacement for PyQt4's WebKit which we
want to drop.

> I'm planning to open an ITP for my project[4] using PyQt and
> (currently) QtWebKit soon, and I'm guessing for at least Eric[5] and
> Calibre[6] this is a problem as well.
> Will Debian also support PyQt's QtWebKit until Qt 6 if possible?
> If not, what will happen with the packages which depend on it?

So to sum up: I will support PyQt's QtWebKit as far as it doesn't become
absolutely impossible to do so.

Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


Reply via email to