Re: PyQt4 and Python 3.0

I should clarify a few things before I embark on a rebuttal:

- I have deployed my code to my end users many times since I started  
to build my PyQt4 compatibility layer (it is not finished yet, and I  
can't afford to stop pushing out bug fixes and new features for a few  
months while I do a rewrite).

- 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.

On Oct 6, 2008, at 2:32 PM, Phil Thompson wrote:
> On Mon, 6 Oct 2008 12:27:42 -0400, Daniel Miller  
> <daniel <at> keystonewood.com>
> wrote:
>>>
>>>> I hope Phil can stick to the really needed stuff. Porting stuff  
>>>> from
>>>> Qt/KDE 3 to 4 has proven to be draining work which I hope to avoid
>>>> having to do again in the near future.
>>>
>>> Which is why I say don't port, rewrite.
>
> Before I start I should point out that I say "rewrite", not  
> "rewrite from
> scratch". My main point is that, when presented with a major change in
> technology then don't try to get away with making as few changes as
> possible - which is what "port" means to me.

Why should I rewrite an entire code base that is working fine and