On Tuesday 14 June 2011, 14:49:16 Nahuel Greco wrote: > Be careful, I think using PyQt3 3.18.1 with SIP 4.12.1 introduces > memory leaks (these are the versions on latest Debian unstable). Don't > know about using SIP 4.12.3. Check my post here: > > http://old.nabble.com/Simple-usage-of-QListView-seems-to-leak-memory-in-P >yQt-3.18.1-td31812404.html
I noticed your post on this list and can confirm your findings. It might be worth to convert your memory leak exploit into C++ just to rule out a Qt bug. Otherwise, this is Phils call (IFAICT, please understand, that PyQt3 bugs are handled with very low priority only, if at all). Pete > Saludos, > Nahuel Greco. > > On Tue, Jun 14, 2011 at 6:28 AM, Hans-Peter Jansen <h...@urpla.net> wrote: > > On Tuesday 14 June 2011, 07:09:27 Vivek Narvekar wrote: > >> Hello, > >> > >> > >> > >> I was previously using SIP 3.3 and PyQt 3.3 versions with Qt 3.0.8. > >> > >> Now I am planning to migrate to QT 3.3.6-8. > > > > This might work, but nobody will care, if it doesn't. > > > >> Can you please tell me if SIP 3.3 and PyQt 3.3 version are compatible > >> with QT 3.3.6-8 ? > > > > Well, being backwards isn't a crime per se, but for your own safety, I > > would strongly advise to use the the latest sip and PyQt3 releases: > > > > sip: 4.12.3 > > PyQt3: 3.18.1 > > > > That way, your PyQt3 code has good chances of still working properly, > > and you have the foundation for using PyQt4 in parallel, too. > > > > Pete > > _______________________________________________ > > PyQt mailing list PyQt@riverbankcomputing.com > > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > _______________________________________________ > PyQt mailing list PyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt