Phil Thompson | 4 Oct 02:07

Re: PyQt4 and Python 3.0

On Fri, 03 Oct 2008 16:45:12 -0700, Glenn Linderman <glenn <at> nevcal.com>
wrote:
> On approximately 10/3/2008 4:25 PM, came the following characters from 
> the keyboard of Phil Thompson:
>> Personally I think "compatibility wrappers" are a waste of time and
>> effort.
>> There are times when you really should rewrite your application (and I
>> don't care how big it is). PyQt4 is a complete rewrite of PyQt3, SIP5
>> will
>> not share any code with SIP4.
>>   
> 
> Interesting philosophy.  Some truth there.  But then it is a big job to 
> do a rewrite, and someone else's release schedule isn't always the right 
> time.

You have a potential problem if one customer wants your app for Py2 and
another for Py3. In reality I don't see that as a major problem as paying
customers are going to be the most conservative. I think it will be a while
before Py3 becomes mainstream.

>> Major transitions (Qt3 => Qt4, Python2 => Python3) should be considered
>> as
>> opportunities for rewrites. They should not be treated as "how can I get
>> from one to the other with as few changes as possible".
>>   
> 
> If the application was old, I might agree.  But here I am, thinking 
> about, and starting to code, a brand new application.
> 
(Continue reading)

Glenn Linderman | 4 Oct 06:29
X-Face
Favicon

Re: PyQt4 and Python 3.0

On approximately 10/3/2008 5:07 PM, came the following characters from
the keyboard of Phil Thompson:
> On Fri, 03 Oct 2008 16:45:12 -0700, Glenn Linderman <glenn <at> nevcal.com>
> wrote:
>   
>> On approximately 10/3/2008 4:25 PM, came the following characters from 
>> the keyboard of Phil Thompson:
>>     
>>> Personally I think "compatibility wrappers" are a waste of time and
>>> effort.
>>> There are times when you really should rewrite your application (and I
>>> don't care how big it is). PyQt4 is a complete rewrite of PyQt3, SIP5
>>> will
>>> not share any code with SIP4.
>>>   
>>>       
>> Interesting philosophy.  Some truth there.  But then it is a big job to 
>> do a rewrite, and someone else's release schedule isn't always the right 
>> time.
>>     
>
> You have a potential problem if one customer wants your app for Py2 and
> another for Py3. In reality I don't see that as a major problem as paying
> customers are going to be the most conservative. I think it will be a while
> before Py3 becomes mainstream.
>   

One would hope they can coexist happily, and that if the application
requires a particular version of Python, that it could be installed...
or... better...
(Continue reading)

Detlev Offenbach | 4 Oct 12:10
Favicon

Re: PyQt4 and Python 3.0

On Samstag, 4. Oktober 2008, Phil Thompson wrote:
> On Fri, 03 Oct 2008 16:45:12 -0700, Glenn Linderman <glenn <at> nevcal.com>
>
> wrote:
> > On approximately 10/3/2008 4:25 PM, came the following characters from
> >
> > the keyboard of Phil Thompson:
> >> Personally I think "compatibility wrappers" are a waste of time and
> >> effort.
> >> There are times when you really should rewrite your application (and I
> >> don't care how big it is). PyQt4 is a complete rewrite of PyQt3, SIP5
> >> will
> >> not share any code with SIP4.
> >
> > Interesting philosophy.  Some truth there.  But then it is a big job to
> > do a rewrite, and someone else's release schedule isn't always the right
> > time.
>
> You have a potential problem if one customer wants your app for Py2 and
> another for Py3. In reality I don't see that as a major problem as paying
> customers are going to be the most conservative. I think it will be a while
> before Py3 becomes mainstream.
>
> >> Major transitions (Qt3 => Qt4, Python2 => Python3) should be considered
> >> as
> >> opportunities for rewrites. They should not be treated as "how can I get
> >> from one to the other with as few changes as possible".
> >
> > If the application was old, I might agree.  But here I am, thinking
> > about, and starting to code, a brand new application.
(Continue reading)


Gmane