Re: [PyQt] PyQt5 roadmap-guesstimate?
On Mon, 7 Jan 2013 11:02:42 -0600, "Jonathan Harper" 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 > > Phil - > > If you are in need of assistance with documentation, put some feelers out > there among PyQt developers. I would be glad to assist in my free time. Thanks - I will. The plan is to write a tool that contributors can use to translate the Qt5 docs from C++ to Python. This will allow updates made to the original docs to be tracked so that corresponding changes to the Python version can be identified as being needed. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 roadmap-guesstimate?
On Mon, 7 Jan 2013 22:07:26 +0800, zw g wrote: > Phil, thank you for the information. > > My question is: > Will PyQt4/PyQt5 eventually support Android and iOS? (After Qt5.x series > support Android & iOS.) PyQt5 will. PyQt4 will so long as the Android and iOS support is a simple port with no API changes. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 roadmap-guesstimate?
On 01/07/2013 06:43 PM, Phil Thompson wrote: On Mon, 07 Jan 2013 18:05:48 +0700, Sebastian Sauer 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. Yes, lot of thanks for the very detailed answer! 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. :) ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 roadmap-guesstimate?
> > 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 Phil - If you are in need of assistance with documentation, put some feelers out there among PyQt developers. I would be glad to assist in my free time. Regards, Jonathan Harper ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Issue of QWebPage.extension
Hello,
you have to cast it explicitly using sip.cast.
Here is a code extract of the eric5 web browser.
if extension == QWebPage.ErrorPageExtension:
info = sip.cast(option, QWebPage.ErrorPageExtensionOption)
errorPage = sip.cast(output, QWebPage.ErrorPageExtensionReturn)
Regards,
Detlev
On Monday 07 January 2013, 21:55:27 Flya Flyaa wrote:
I want to get page detailed error message this
way: http://stackoverflow.com/questions/7279046/how-to-get-detailed-error-
message-when-qtwebkit-fails-to-load-a-page
This need reimplement QWebPage.extension
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qwebpage.html#extension,
and get detail from the second argument ExtensionOption.
Code like this:
def extension(self, extension, info = None, errorPage = None):
if extension == QtWebKit.QWebPage.ErrorPageExtension:
content = u"Failed loading
pageFailed loading page (%s)%s
" % (info.errorString, info.url.toString())
errorPage.content = QtCore.QByteArray(content.encode('utf-8'))
gdata.log(u'Warn: Failed loading [%s] (%s)!' % (info.errorString,
info.url.toString() ))
return True
return True
When extension == QtWebKit.QWebPage.ErrorPageExtension, the second argument
should be QWebPage.ErrorPageExtensionOption, but it always
be QWebPage.ExtensionOption, and can't get the detailed error message from it.
PySide has this problem in earlier versions, it be fixed later with test
case
http://pyside.sourcearchive.com/documentation/1.0.1-1/bug__694_8py_source.html
. Hope PyQt can fix it.
--
Detlev Offenbach
det...@die-offenbachs.de___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 roadmap-guesstimate?
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 wrote: > On Mon, 07 Jan 2013 18:05:48 +0700, Sebastian Sauer 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 listPyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Issue with latest PyQt4 and Qt5
Hello, I am facing an issue with latest PyQt4 snapshot and Qt5. It seems that the 'setSocketDescriptor()' method of 'QAbstractSocket' is not working correctly, if PyQt4 is compiled against Qt5. How to reproduce it? Just start the threadedfortunes.py script of the examples. Therafter follow the instructions given. Trying to get a fortune via the fortuneclient.py script makes the later script hang (i.e. no fortune is returned). It seems, that the socket is not connected in the server, which uses the incomingConnection() method of QTcpServer. The same issue happens with eric5 and Qt5 in the Cooperation functions. eric5 and the a.m. example both work fine with PyQt4 built against Qt4. Please note, that the signature of setSocketDescriptor method is different between Qt4 and Qt5. In Qt4 it is using an 'int' and in Qt5 a 'qintptr'. However, the type of the descriptor passed to the QTcpServer,incomingConnection() call is sip.voidptr (for Qt5). Regards, Detlev -- Detlev Offenbach det...@die-offenbachs.de___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Issue of QWebPage.extension
I want to get page detailed error message this way:
http://stackoverflow.com/questions/7279046/how-to-get-detailed-error-message-when-qtwebkit-fails-to-load-a-page
This need reimplement QWebPage.extension
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qwebpage.html#extension,
and get detail from the second argument ExtensionOption.
Code like this:
def extension(self, extension, info = None, errorPage = None):
if extension == QtWebKit.QWebPage.ErrorPageExtension:
content = u"Failed loading
pageFailed loading page (%s)%s
" % (info.errorString, info.url.toString())
errorPage.content = QtCore.QByteArray(content.encode('utf-8'))
gdata.log(u'Warn: Failed loading [%s] (%s)!' %
(info.errorString, info.url.toString() ))
return True
return True
When extension == QtWebKit.QWebPage.ErrorPageExtension, the second argument
should be QWebPage.ErrorPageExtensionOption, but it always
be QWebPage.ExtensionOption, and can't get the detailed error message from
it.
PySide has this problem in earlier versions, it be fixed later with test
case
http://pyside.sourcearchive.com/documentation/1.0.1-1/bug__694_8py_source.html.
Hope PyQt can fix it.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 roadmap-guesstimate?
On Mon, 07 Jan 2013 18:05:48 +0700, Sebastian Sauer 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 listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] PyQt5 roadmap-guesstimate?
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! ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
