bzr-windows team mailing list archive

[Gary van der Merwe <garyvdm@xxxxxxxxx>]

On 22/01/2010 07:30, Alexander Belchenko wrote:
> Ian Clatworthy пишет:
> > John Arbash Meinel wrote:
> >
> > > For simplicity, I'd like to stick with python2.5 and PyQt 4.4 for this
> > > release. We can look at bumping it to py 2.6 + PyQt >= 4.6 for the
> > > next one.
> >
> > I wonder whether we'd be better served by having our Windows users
> > running on the same PyQt release as our Ubuntu and OS X users? Lucid
> > currently has 4.6.0 and I believe the OS X installers are bundling 4.6.x.
>
> IIRC, Gary said that 4.6.0 has the bug affected QBzr (at least its test
> suite).

https://bugs.launchpad.net/bugs/411999 , which is fixed by pyqt 4.6.1. 
It dose not seem to cause any real bugs, but I should really file a SRU 
for karmic.

> > Disclaimer: My motivation here is slightly selfish. I accidentally
> > started using some post 4.4 APIs to tune widget layouts recently. I'll
> > go through and make them conditional on the right version of Qt being
> > installed today. Even so, it always feels odd to me to not take
> > advantage of APIs offering a better user experience without a compelling
> > reason. In the case of Windows (unlike most Linux distros), *we* get to
> > dictate the Qt version so I feel we ought to take the latest unless
> > there's clear evidence it's a bad idea.
> >
> > I agree that sticking with py 2.5 + PyQt 4.4 is the easiest answer right
> > now. OTOH, rc1 has a few weeks of testing time up its sleeve so we
> > *could* upgrade now and address any issues as they come up. Could we try
> > PtQt 4.6.x in combination with Python 2.5 say?

PtQt 4.6.x never had windows builds for Python 2.5, only 2.6. PtQt 4.7.x 
fixes this.