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 d
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
On Oct 7, 2008, at 12:54 PM, Phil Thompson wrote:
On Tue, 7 Oct 2008 11:10:57 -0400, Daniel Miller
<[EMAIL PROTECTED]>
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 con
On 10/7/2008 5:10 PM, Daniel Miller wrote:
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 f
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 re
On Oct 7, 2008, at 6:10 AM, Phil Thompson wrote:
And we could have just as many Viper versions as we'd damn well
please
within any given Python and Qt release timeframe -- we'd simply
import
from Viper2, Viper3... rather than Viper.
Thoughts?
With 20/20 hindsight (starting 10 years ago)
On Sun, 05 Oct 2008 14:11:45 +0200, Simon Edwards <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> Phil Thompson wrote:
>> 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
Hello,
Phil Thompson wrote:
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".
I thought the way the Python guys handled Python 3 was very go
On Samstag, 4. Oktober 2008, Phil Thompson wrote:
> On Fri, 03 Oct 2008 16:45:12 -0700, Glenn Linderman <[EMAIL PROTECTED]>
>
> wrote:
> > On approximately 10/3/2008 4:25 PM, came the following characters from
> >
> > the keyboard of Phil Thompson:
> >> Personally I think "compatibility wrappers" a
On sab, 2008-10-04 at 00:25 +0100, Phil Thompson wrote:
> On the other hand, if you did write it correctly in the first place
> (something I've never managed) PyQt4 for Python2 will be maintained
> for several years - certainly while new versions of Python2 are
> released.
This is good to know, s
On Fri, 03 Oct 2008 16:45:12 -0700, Glenn Linderman <[EMAIL PROTECTED]>
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 rea
On Fri, 03 Oct 2008 12:42:53 -0700, Glenn Linderman <[EMAIL PROTECTED]>
wrote:
> On approximately 10/3/2008 8:18 AM, came the following characters from
> the keyboard of Phil Thompson:
>> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Hi,
>>>
>>> will t
On Fri, Oct 3, 2008 at 9:59 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
> On 2008-10-03, Paul A. Giannaros wrote:
>> On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
>> > On 2008-10-03, Phil Thompson wrote:
>> >> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
>>
On 03.10.08 21:59:14, Mark Summerfield wrote:
> On 2008-10-03, Paul A. Giannaros wrote:
> > On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
> > > On 2008-10-03, Phil Thompson wrote:
> > >> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
> > >
> > > Here's my personal
On Fri, Oct 3, 2008 at 4:05 PM, Glenn Linderman <[EMAIL PROTECTED]> wrote:
[ snip ]
> My personal situation is that I have only recently begun writing my
> first major PyQt application, using Python 2.5 and PyQt 4. This will
> take me "a while" also. Depending on how long our "a while"s are, I
>
On Fri, Oct 3, 2008 at 3:59 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
> On 2008-10-03, Paul A. Giannaros wrote:
>> On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
>> > On 2008-10-03, Phil Thompson wrote:
>> >> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
>>
On 2008-10-03, Paul A. Giannaros wrote:
> On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
> > On 2008-10-03, Phil Thompson wrote:
> >> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
> >
> > Here's my personal "wish list" for Python 3/PyQt4 (including those that
> >
On Oct 3, 2008, at 2:15 PM, Paul A. Giannaros wrote:
On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]>
wrote:
On 2008-10-03, Phil Thompson wrote:
On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
Here's my personal "wish list" for Python 3/PyQt4 (including those
that
P
On Fri, Oct 3, 2008 at 5:08 PM, Mark Summerfield <[EMAIL PROTECTED]> wrote:
> On 2008-10-03, Phil Thompson wrote:
>> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
> Here's my personal "wish list" for Python 3/PyQt4 (including those that
> Phil is going to do as he says above):
>
> - No QStrin
On 2008-10-03, Phil Thompson wrote:
> On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
>
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > will there be PyQt4 support for Python 3.0 once it goes final?
>
> Not straight away. I will take the opportunity to break backwards
> compatibility (eg. removing
On Fri, 3 Oct 2008 17:11:19 +0200, Detlev Offenbach
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> will there be PyQt4 support for Python 3.0 once it goes final?
Not straight away. I will take the opportunity to break backwards
compatibility (eg. removing QVariant, QString, QChar, QByteArray etc), and
thos
Hi,
will there be PyQt4 support for Python 3.0 once it goes final?
Regards,
Detlev
--
Detlev Offenbach
[EMAIL PROTECTED]
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
22 matches
Mail list logo
