On Fri, Dec 17, 2010 at 12:48 PM, Brian Zambrano wrote:
> Building a universal version of my commercial PyQt has worked for me in the
> past with these steps:
>
> sip:
>
> $ python configure.py --universal
> $ make && sudo make install
>
> PyQt:
>
> $ python configure.py --confirm-license
> $ make
We're seeing a change in behavior in the latest PyQt4.
We have a custom QStandardItemModel with custom QStandardItems. It is being
used by a QTreeView.
When calling tree.invisibleRootItem().child(i) we are getting back
QtGui.QStandardItem instances instead of our custom classes.
This seemed rel
David Aguilar gmail.com> writes:
>
> We're seeing a change in behavior in the latest PyQt4.
>
> We have a custom QStandardItemModel with custom QStandardItems. It is being
> used by a QTreeView.
>
> When calling tree.invisibleRootItem().child(i) we are getti
Phil Thompson riverbankcomputing.com> writes:
>
> On Mon, 29 Apr 2013 20:41:46 +0000 (UTC), David Aguilar
gmail.com>
> wrote:
> > We're seeing a change in behavior in the latest PyQt4.
> > When calling tree.invisibleRootItem().child(i) we are getting back
&
Matti Aarnio reported a memory leak in git-cola that I traced back to PyQt4.
I've attached a minimal reproducer.
I've tested this on Mac OS X and Debian/testing with PyQt4 4.9.x.
Matti's tried it on x86_64 Fedora 18, we see the same behavior there.
Everytime we hit the "Refresh" button more mem