[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyQt] PyQt5 roadmap-guesstimate?
From: zw g <pekingmaster () gmail ! com>
Date: 2013-01-07 14:07:26
Message-ID: CAMXG_XpgSNYp52xR2KY5eZnqGVVv3bnyFC_65T+5SzpCbCqkcw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Phil, thank you for the information.
My question is:
Will PyQt4/PyQt5 eventually support Android and iOS? (After Qt5.x series
support Android & iOS.)
Gui
On Mon, Jan 7, 2013 at 7:43 PM, Phil Thompson
<phil@riverbankcomputing.com>wrote:
> On Mon, 07 Jan 2013 18:05:48 +0700, Sebastian Sauer <mail@dipe.org> wrote:
> > Hi,
> >
> > reading the backlogs and all I was able to find related to support for
> > PyQt@Qt5 its great to see that PyQt4 does support Qt5 already. Fantastic
>
> > work as usual Phil!
> >
> > My question is direct related to PyQt5, so not PyQt4. I read that the
> > plan is to replace QString/QVariant with Python objects but beside that
> > there are not much informations around related to PyQt5.
> >
> > So, is there any guesstimate or maybe even a roadmap when we can expect
> > to see PyQt5? Also I wonder if now that PyQt4 does proper support Qt4
> > and Qt5 has PyQt5 any priority? Is it supposed to replace PyQt4 let's
> > say next n years or will PyQt4 live on during Qt5 lifetime (I think yes,
>
> > but cannot harm to ask I think :) ).
> >
> > Thanks in advance and keep up the great work!
>
> The priority for PyQt5 is certainly lower than it was originally because
> of the amount of stuff that was removed from Qt5. In other words, Qt v5.0
> doesn't offer much over Qt4. That will change once Digia sort out their
> resourcing of what was originally planned for Qt5, presumably starting with
> Qt v5.1.
>
> Adding Qt5 support to PyQt4 was a lot of work, but it will all be re-used
> in PyQt5. The main remaining work to do for PyQt5 is to change the build
> system. There are two drivers for this...
>
> - SIP5 will not include a build system so PyQt will need a self-contained
> build system
>
> - to support cross-compilation (for Raspberry Pi and, eventually, Android
> and iOS).
>
> ...and the always problematic documentation.
>
> I don't plan on dropping support for PyQt4 - lots of people will want to
> take advantage of bug fixes in Qt5, and its support for additional devices,
> without porting from PyQt4 to PyQt5.
>
> At this stage I'm not going to give any dates, but most of the work for an
> initial PyQt5 release has already been done.
>
> Phil
> _______________________________________________
> PyQt mailing list PyQt@riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
[Attachment #5 (text/html)]
<div dir="ltr">Phil, thank you for the information.<div><br></div><div>My question \
is:<br><div style>Will PyQt4/PyQt5 eventually support Android and iOS? (After Qt5.x \
series support Android & iOS.)</div></div></div><div class="gmail_extra">
<br clear="all"><div>Gui</div>
<br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 7:43 PM, Phil Thompson <span \
dir="ltr"><<a href="mailto:phil@riverbankcomputing.com" \
target="_blank">phil@riverbankcomputing.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div class="im">On Mon, 07 Jan 2013 18:05:48 +0700, Sebastian Sauer <<a \
href="mailto:mail@dipe.org">mail@dipe.org</a>> wrote:<br> > Hi,<br>
><br>
> reading the backlogs and all I was able to find related to support for<br>
> PyQt@Qt5 its great to see that PyQt4 does support Qt5 already. Fantastic<br>
<br>
> work as usual Phil!<br>
><br>
> My question is direct related to PyQt5, so not PyQt4. I read that the<br>
> plan is to replace QString/QVariant with Python objects but beside that<br>
> there are not much informations around related to PyQt5.<br>
><br>
> So, is there any guesstimate or maybe even a roadmap when we can expect<br>
> to see PyQt5? Also I wonder if now that PyQt4 does proper support Qt4<br>
> and Qt5 has PyQt5 any priority? Is it supposed to replace PyQt4 let's<br>
> say next n years or will PyQt4 live on during Qt5 lifetime (I think yes,<br>
<br>
> but cannot harm to ask I think :) ).<br>
><br>
> Thanks in advance and keep up the great work!<br>
<br>
</div>The priority for PyQt5 is certainly lower than it was originally because<br>
of the amount of stuff that was removed from Qt5. In other words, Qt v5.0<br>
doesn't offer much over Qt4. That will change once Digia sort out their<br>
resourcing of what was originally planned for Qt5, presumably starting with<br>
Qt v5.1.<br>
<br>
Adding Qt5 support to PyQt4 was a lot of work, but it will all be re-used<br>
in PyQt5. The main remaining work to do for PyQt5 is to change the build<br>
system. There are two drivers for this...<br>
<br>
- SIP5 will not include a build system so PyQt will need a self-contained<br>
build system<br>
<br>
- to support cross-compilation (for Raspberry Pi and, eventually, Android<br>
and iOS).<br>
<br>
...and the always problematic documentation.<br>
<br>
I don't plan on dropping support for PyQt4 - lots of people will want to<br>
take advantage of bug fixes in Qt5, and its support for additional devices,<br>
without porting from PyQt4 to PyQt5.<br>
<br>
At this stage I'm not going to give any dates, but most of the work for an<br>
initial PyQt5 release has already been done.<br>
<span class="HOEnZb"><font color="#888888"><br>
Phil<br>
</font></span><div class="HOEnZb"><div \
class="h5">_______________________________________________<br> PyQt mailing list \
<a href="mailto:PyQt@riverbankcomputing.com">PyQt@riverbankcomputing.com</a><br> <a \
href="http://www.riverbankcomputing.com/mailman/listinfo/pyqt" \
target="_blank">http://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br> \
</div></div></blockquote></div><br></div>
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic