[PyQt] ANN: automated daily snapshot builds for PyQt and friend on openSUSE build service
[Sorry for cross posting] Hi PyQtnistas, I proudly announce the availability of automated builds of the most current PyQt and related packages including snapshots on openSUSEs build service for openSUSE 11.1, 11.2 and 11.3, here: https://build.opensuse.org/project/monitor?project=home%3Afrispete%3APyQt https://build.opensuse.org/project/monitor?project=home%3Afrispete%3APyQt-next New sip4, PyQt3 and PyQt4 snapshots and release get build against a range of gcc and Qt versions automatically, e.g. without human intervention (if all goes well, famous last words..). dip and PyQtMobility will probably follow soon. If you add both home:frispete:PyQt home:frispete:PyQt-next to your list of repos, than you get the current snapshot builds of qscintilla, sip4, PyQt3 and PyQt4, with dependent packages, like PyQwt5, PyKDE3 and PyKDE4. Omitting or deactivating the latter, you can switch back to the current released versions with: zypper dup -r home_frispete_PyQt BTW, home:frispete:PyQt contains the builds of the current versions of a lot of our favorite stuff: e.g. eric4, PyQwt5. eric is lacking the newest release, but I didn't manage to automate the sourceforge download process, yet. How to choose your target? Depending on which other repos you're using, choose your target accordingly, e.g. if you have the KDE:Distro:Stable (KDE 4.4) repo included, use KDE_Distro_Stable_openSUSE_11.x, KDE_Distro_Factory_openSUSE_11.x for KDE:Distro:Factory (KDE 4.5), or none of them, then use plain openSUSE_11.x. Note, that you implicitely choose your systems Qt4 version with this decision. I hope, this fullfills the most common needs. PyKDE4 is only provided for KDE_Distro_Stable_x ATM, since I didn't got around splitting this package into a 4.4 and 4.5 version. All in all, these repos provide the the cheapest way of keeping current with the PyQt project, that I know of. Comments welcome. Enjoy, Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next PyQt and SIP Releases
On Wed, Oct 13, 2010 at 3:13 PM, Phil Thompson p...@riverbankcomputing.com wrote: On Wed, 13 Oct 2010 11:50:21 -0400, Darren Dale dsdal...@gmail.com wrote: On Tue, Oct 12, 2010 at 8:12 AM, Phil Thompson p...@riverbankcomputing.com wrote: The current PyQt and SIP snapshots can be considered release candidates. Now is a good time to check them against your favorite applications. I just installed qt-4.7 on snow leopard, using macports (using a custom portfile with very minor changes, see http://trac.macports.org/ticket/26646). I installed the most recent sip and pyqt4 snapshots for python-2.6 and python-2.7, and then the dip snapshot. When I run the dip testsuite with either python version, it stalls and shows a dialog with a spinbox containing 10 and cancel and ok buttons. I have to give focus to this dialog box, at which point it closes, and then many more widgets are opened and closed in rapid succession. I don't recall the widgets rendering before now. Changes to the automate module are the cause of that. Here is the resulting test report: ..F...F == FAIL: test_list (tests.dip_ui.test_mapping.TestMapping) Test list attributes of a mapping. -- Traceback (most recent call last): File /Users/darren/Downloads/dip-py2-gpl-0.3-snapshot-4deec720d5c2/test/tests/dip_ui/test_mapping.py, line 81, in test_list self.assertEqual(model['attr'], ['first', '2nd']) AssertionError: Lists differ: ['first', 'second'] != ['first', '2nd'] First differing element 1: second 2nd - ['first', 'second'] ? + ['first', '2nd'] ? ^ == FAIL: test_List (tests.dip_ui.test_model.TestModel) Test List attributes of a model. -- Traceback (most recent call last): File /Users/darren/Downloads/dip-py2-gpl-0.3-snapshot-4deec720d5c2/test/tests/dip_ui/test_model.py, line 215, in test_List self.assertEqual(model.attr, ['first', '2nd']) AssertionError: ['first', 'second'] != ['first', '2nd'] -- Ran 247 tests in 111.221s FAILED (failures=2) It looks like the dialog issue showed up in the fifth test before the first failure. Is there a way to print a more verbose report, so in the future I can do a better job identifying which tests contain unreported issues? What you've included in the above is fine. I usually remember to run the tests before pushing to the website so, if there is still a failure, it would appear to be platform specific. I just tested the latest snapshots with python2.6 on Kubuntu Maverick. It is still possible to run the test suite without unittest2 installed for py26, it yields a long list of attribute errors rather than raising an import error during initialization. After installing unittest2, the test suite ran without errors or failures. Also, the test suite ran to completion without requiring any of the dialogs receive focus. So it appears you were right, the issues I reported look to be specific to OS X. Darren ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] [Eric] ANN: automated daily snapshot builds for PyQt and friend on openSUSE build service
On Donnerstag, 14. Oktober 2010, Hans-Peter Jansen wrote: [Sorry for cross posting] Hi PyQtnistas, I proudly announce the availability of automated builds of the most current PyQt and related packages including snapshots on openSUSEs build service for openSUSE 11.1, 11.2 and 11.3, here: https://build.opensuse.org/project/monitor?project=home%3Afrispete%3APyQt https://build.opensuse.org/project/monitor?project=home%3Afrispete%3APyQt-n ext New sip4, PyQt3 and PyQt4 snapshots and release get build against a range of gcc and Qt versions automatically, e.g. without human intervention (if all goes well, famous last words..). dip and PyQtMobility will probably follow soon. If you add both home:frispete:PyQt home:frispete:PyQt-next to your list of repos, than you get the current snapshot builds of qscintilla, sip4, PyQt3 and PyQt4, with dependent packages, like PyQwt5, PyKDE3 and PyKDE4. Omitting or deactivating the latter, you can switch back to the current released versions with: zypper dup -r home_frispete_PyQt BTW, home:frispete:PyQt contains the builds of the current versions of a lot of our favorite stuff: e.g. eric4, PyQwt5. eric is lacking the newest release, but I didn't manage to automate the sourceforge download process, yet. Why don't you get the software via the eric repositories? See the eric web page for details. Do you provide packages to be used with Python3 as well? How to choose your target? Depending on which other repos you're using, choose your target accordingly, e.g. if you have the KDE:Distro:Stable (KDE 4.4) repo included, use KDE_Distro_Stable_openSUSE_11.x, KDE_Distro_Factory_openSUSE_11.x for KDE:Distro:Factory (KDE 4.5), or none of them, then use plain openSUSE_11.x. Note, that you implicitely choose your systems Qt4 version with this decision. I hope, this fullfills the most common needs. PyKDE4 is only provided for KDE_Distro_Stable_x ATM, since I didn't got around splitting this package into a 4.4 and 4.5 version. All in all, these repos provide the the cheapest way of keeping current with the PyQt project, that I know of. Comments welcome. Enjoy, Pete ___ Eric mailing list e...@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/eric -- Detlev Offenbach det...@die-offenbachs.de ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Syntax for connecting to QGraphicsScene.changed signal?
QGraphicsScene's changed signal is documented as: void changed (const QListQRectF) The Qt Utility classes and their Python equivalents section of Chapter 10 Qt Class Hierarchy of GUI Programming with Python: QT Edition (from http://www.commandprompt.com/community/pyqt/x3738) says: You can always use a Python list wherever a QList is needed. But defining a signal as: sceneChanged = QtCore.pyqtSignal(list) and then doing: self._scene.changed.connect(self.sceneChanged) results in the following exception: TypeError: connect() failed between changed(QListQRectF) and sceneChanged() As a workaround, I was able to do the following: @QtCore.pyqtSlot(list) def changed (self, rects): self.sceneChanged.emit(rects) With the following connect() statement: self._scene.changed.connect(self.changed) But how can I directly connect my signal to QGraphicScene's changed signal without going through an intermediate python method? ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python Commander in PyQt?
On Thu Oct 14 00:59:11 BST 2010, Glenn Linderman wrote: So then I started looking for front ends that I could tweak to speak HTTP to a custom CGI script. That's where I started this thread, and why I picked this group to ask in, because I'd find it useful and interesting educationally to tweak a PyQt front end, instead of one written in some other environment. If I understood you correctly, you're looking for a file browser, in which case it might be worth looking at these pages for inspiration: http://lateral.netmanagers.com.ar/stories/29.html http://code.google.com/p/pydingo/ David ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
