headers
Daniel Miller | 7 Oct 20:47

Re: PyQt4 and Python 3.0


On Oct 7, 2008, at 12:54 PM, Phil Thompson wrote:
> On Tue, 7 Oct 2008 11:10:57 -0400, Daniel Miller  
> <daniel <at> keystonewood.com>
> wrote:
>>
>> - I am moving to PyQt4 because I need to use some of the new features
>> (the Graphics View Framework, for one). If I did not need these new
>> features in PyQt4 I'd be content to stay with PyQt3.
>>
>> ...
>>
>> Why should I rewrite an entire code base that is working fine and
>> does not need to be touched?
>
> Obviously you shouldn't if it is meeting your current and anticipated
> requirements.

It doesn't, see above.

> PyQt3 has always maintained backwards compatibility, so has PyQt4.  
> PyQt3 is
> not PyQt4. Likewise Qt3 is not Qt4. Granted, Trolltech produced a  
> Qt3=>Qt4
> migration tool, but then they have orders of magnitude more  
> development
> resources and charge a lot more money for their product.

You have a good point there. I should apologize for being so harsh. I  
guess I'm just frustrated that I have to do so much work to get to
(Continue reading)

Permalink | Reply |
headers
David Boddie | 7 Oct 22:05

Re: PyQt4 and Python 3.0

On Tue Oct 7 19:47:00 BST 2008, Daniel Miller wrote:
> On Oct 7, 2008, at 12:54 PM, Phil Thompson wrote:

> > PyQt3 has always maintained backwards compatibility, so has PyQt4.
> > PyQt3 is not PyQt4. Likewise Qt3 is not Qt4. Granted, Trolltech
> > produced a Qt3=>Qt4 migration tool, but then they have orders of
> > magnitude more development resources and charge a lot more money for
> > their product.
>
> You have a good point there. I should apologize for being so harsh. I
> guess I'm just frustrated that I have to do so much work to get to
> the point where I can actually start using PyQt4. I am really looking
> forward to it...

It's good to hear that you _are_ looking forward to using it, and see
the advantages. You seem to be aware of the differences in style between
the two versions, and that will be very useful.

Although you're having to port to PyQt4 as the result of a Qt 4 feature
(Graphics View), you're quite fortunate to be porting be able to port this
late in the Qt 4.x series when most of the feature gaps of Qt 4.0 have been
filled.

[...]

> > Every place? Surely you only use QSettings in one place?
>
> Well, yes of course. Sorry for picking a bad example. How about
> QSplitter, QPushButton, QProgressBar, QPopumMenu, etc. Those are
> definitely used in many places, and the API for each of them changed.
(Continue reading)

Permalink | Reply |
headers
Andreas Pakulat | 7 Oct 22:26
Gravatar

Re: PyQt4 and Python 3.0

On 07.10.08 14:47:00, Daniel Miller wrote:
> Well, yes of course. Sorry for picking a bad example. How about  
> QSplitter, QPushButton, QProgressBar, QPopumMenu, etc. Those are  
> definitely used in many places, and the API for each of them changed. I 
> realize this is not your fault--it was a decision made by Trolltech. 
> However, I feel like they did more to help their users migrate old code 
> bases to Qt4.

They didn't. The qt3to4 tool is a joke when you try to migrate a real-world
large codebase, it barely provides a starting point. Also it forces you
into the Qt3Support classes, code thats barely maintained by TT - they only
fix the worst bugs in those parts.

So, the C++ migrators don't really have more help than the PyQt4 users.

>>>> Note that I wouldn't call the Q3Support classes a compatibility  
>>>> layer.
>>>
>>> I agree. In a C++ app it might be possible (even simple?) to do
>>> global find/replace ...
>>
>> You are seriously suggesting that PyQt4 should include a full  
>> emulation of
>> the PyQt3 API???
>
> Why not? Is it too much to expect a widely used library to have backward 
> compatibility between versions?

Yes, if there's basically just 1 person doing the work and he's expected to
offer an opensource version and a not-that-expensive commercial version.
(Continue reading)

Permalink | Reply |

Gmane