[PyQt] PyQt Development Roadmap Published
Phil Thompson
phil at riverbankcomputing.com
Tue Oct 21 18:40:00 BST 2008
On Tue, 21 Oct 2008 19:27:55 +0200, Detlev Offenbach
<detlev at die-offenbachs.de> wrote:
> On Montag, 20. Oktober 2008, Phil Thompson wrote:
>> On Mon, 20 Oct 2008 21:13:30 +0200, Detlev Offenbach
>>
>> <detlev at die-offenbachs.de> wrote:
>> > On Montag, 20. Oktober 2008, Phil Thompson wrote:
>> >> I've published a development roadmap for PyQt at
>> >> http://www.riverbankcomputing.com/software/pyqt/roadmap.
>> >>
>> >> It describes my current thinking - but everything is still up for
>> >> grabs.
>> >> It's not intended to capture every planned change - but I do want to
>> >> identify every incompatible change.
>> >>
>> >> Comments and suggestions welcome.
>> >
>> > Will the new pyqtSignal have a requirement on the Python version (i.e.
>>
>> 2.6)
>>
>> > because the given example will not work on Python 2.5.x. Same applies
>> > to
>> > your
>> > pyqtSlot example.
>>
>> Why not? What have I missed?
>
> Named arguments and *args reversed. Up to 2.6 I think, you have to have
> args
> first followed by named args followed by *args followed by **kwargs.
I was just using Python to describe the API. The implementation will be in
C which doesn't have those restrictions.
>> > Removal of Non-Pythonic Classes:
>> > Do we have to change the whole application to use the new API (version
>> > 2)
>> > or
>> > can this be done on a module by module basis as well? The later would
>>
>> ease
>>
>> > porting of existing applications.
>>
>> The whole application.
>
> That means I have to change possibly thousands of lines of code first and
> test
> them as a whole?
Yes, otherwise you will have two different implementations of the same type
flying around your application.
Phil
More information about the PyQt
mailing list