Mailing List Archive: Maemo: Developers

PyQt

Index | Next | Previous | View Threaded

maemo at csipa

Nov 17, 2009, 11:25 AM

Post #1 of 5 (1062 views)
Permalink

PyQt

I have a question about PyQt, but not a technical one :)

Can someone enlighten me about the 'official' status of PyQt in Maemo ? I
understand Nokia folks who have been working on it now concentrate on PySide,
but it's a bit unclear if there is an official stance on it or not, both
regarding existing PyQt packages in Diablo and about future versions in
Fremantle. I have taken the liberty to push (missing) PyQt packages from
Diablo to Fremantle repositories some time ago. I also happen to have up-to-
date PyQt versions for Diablo and Fremantle in my local scratchbox but am a
bit hesitant to overwrite/update the current packages. Do we (still) have
active maintainers ?

To clarify once more, I have nothing against PySide efforts, on the contrary, I
endorse and watch PySide closely, but I think people who do not care about
LGPL should have the option of using all bindings available, especially since
they're (mostly) API compatible.

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

matti.p.airas at nokia

Nov 18, 2009, 2:30 AM

Post #2 of 5 (967 views)
Permalink

Re: PyQt [In reply to]

Hi, Attila!

I'm managing Nokia contributions to the PySide and PyMaemo community
projects, so here's my stance: you're right that we're focusing our
efforts on PySide and we won't be investing in PyQt ports any longer. If
you're interested in maintaining PyQt on Maemo in the future, maybe you
could arrange with Luciano Wolf and/or Phil Thompson (the current PyQt
garage project admins) to have you appointed as a new project admin?

Since there are no active maintainers for PyQt on Maemo, I think you
should feel free to update the packages in any case.

Having said all this, I strongly encourage Python Qt developers on Maemo
to use PySide instead of PyQt. We'll be generating our future Maemo 6
API bindings using PySide, so if you want to be able to utilize them,
you'll need to go with PySide in any case. In addition, having only one
set of Python Qt binding libraries on the device is probably greatly
preferable to the end user. I understand PySide is at the moment a bit
rough, but the situation will improve a lot by the end of the year.

Cheers,

ma.

ext Attila Csipa wrote:
> I have a question about PyQt, but not a technical one :)
>
> Can someone enlighten me about the 'official' status of PyQt in Maemo ? I
> understand Nokia folks who have been working on it now concentrate on PySide,
> but it's a bit unclear if there is an official stance on it or not, both
> regarding existing PyQt packages in Diablo and about future versions in
> Fremantle. I have taken the liberty to push (missing) PyQt packages from
> Diablo to Fremantle repositories some time ago. I also happen to have up-to-
> date PyQt versions for Diablo and Fremantle in my local scratchbox but am a
> bit hesitant to overwrite/update the current packages. Do we (still) have
> active maintainers ?
>
> To clarify once more, I have nothing against PySide efforts, on the contrary, I
> endorse and watch PySide closely, but I think people who do not care about
> LGPL should have the option of using all bindings available, especially since
> they're (mostly) API compatible.
>
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

maemo at csipa

Nov 19, 2009, 9:12 AM

Post #3 of 5 (959 views)
Permalink

Re: PyQt [In reply to]

On Wednesday 18 November 2009 11:30:32 Matti Airas wrote:
> you're interested in maintaining PyQt on Maemo in the future, maybe you
> could arrange with Luciano Wolf and/or Phil Thompson (the current PyQt
> garage project admins) to have you appointed as a new project admin?

> Since there are no active maintainers for PyQt on Maemo, I think you
> should feel free to update the packages in any case.

I have written to both persons in question and had a positive response from
Phil Thompson, still waiting for Luciano's response.

> Having said all this, I strongly encourage Python Qt developers on Maemo
> to use PySide instead of PyQt. We'll be generating our future Maemo 6
> API bindings using PySide, so if you want to be able to utilize them,
> you'll need to go with PySide in any case. In addition, having only one
> set of Python Qt binding libraries on the device is probably greatly
> preferable to the end user. I understand PySide is at the moment a bit
> rough, but the situation will improve a lot by the end of the year.

PyQt can _at least_ serve as a stopgap till then, especially since people can
use the tried and true PyQt today without fearing the rough edges of PySide,
and then switch if they think PySide has reached a point where it benefits
them more. The worst case scenario is IMHO people not using *either*
(potentially giving up on development altogether), PyQt because they fear
it's abandoned, and PySide because it's just not ready for prime-time yet.

As for having two bindings, well, true, but then again, end users don't care
about GTK vs Qt and they'll have to have both in the future, just as they do
on the (Linux) desktop.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

khertan at khertan

Nov 19, 2009, 9:19 AM

Post #4 of 5 (952 views)
Permalink

Re: PyQt [In reply to]

"PyQt because they fear
it's abandoned, and PySide because it's just not ready for prime-time yet."

This is clearly why i'ven't yet did the switch from gtk ...

2009/11/19 Attila Csipa <maemo [at] csipa>

> On Wednesday 18 November 2009 11:30:32 Matti Airas wrote:
> > you're interested in maintaining PyQt on Maemo in the future, maybe you
> > could arrange with Luciano Wolf and/or Phil Thompson (the current PyQt
> > garage project admins) to have you appointed as a new project admin?
>
> > Since there are no active maintainers for PyQt on Maemo, I think you
> > should feel free to update the packages in any case.
>
> I have written to both persons in question and had a positive response from
> Phil Thompson, still waiting for Luciano's response.
>
> > Having said all this, I strongly encourage Python Qt developers on Maemo
> > to use PySide instead of PyQt. We'll be generating our future Maemo 6
> > API bindings using PySide, so if you want to be able to utilize them,
> > you'll need to go with PySide in any case. In addition, having only one
> > set of Python Qt binding libraries on the device is probably greatly
> > preferable to the end user. I understand PySide is at the moment a bit
> > rough, but the situation will improve a lot by the end of the year.
>
> PyQt can _at least_ serve as a stopgap till then, especially since people
> can
> use the tried and true PyQt today without fearing the rough edges of
> PySide,
> and then switch if they think PySide has reached a point where it benefits
> them more. The worst case scenario is IMHO people not using *either*
> (potentially giving up on development altogether), PyQt because they fear
> it's abandoned, and PySide because it's just not ready for prime-time yet.
>
> As for having two bindings, well, true, but then again, end users don't
> care
> about GTK vs Qt and they'll have to have both in the future, just as they
> do
> on the (Linux) desktop.
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

--
Benoît HERVIER - http://khertan.net/

luciano.wolf at indt

Nov 19, 2009, 9:23 AM

Post #5 of 5 (952 views)
Permalink

RE: PyQt [In reply to]

Hi Attila,

You've green light to go on! :)

Regards,
Luciano

________________________________________
From: maemo-developers-bounces [at] maemo [maemo-developers-bounces [at] maemo] On Behalf Of ext Attila Csipa [maemo [at] csipa]
Sent: Thursday, November 19, 2009 15:12
To: Airas Matti.P (Nokia-D/Tampere)
Cc: maemo-developers [at] maemo
Subject: Re: PyQt

On Wednesday 18 November 2009 11:30:32 Matti Airas wrote:
> you're interested in maintaining PyQt on Maemo in the future, maybe you
> could arrange with Luciano Wolf and/or Phil Thompson (the current PyQt
> garage project admins) to have you appointed as a new project admin?

> Since there are no active maintainers for PyQt on Maemo, I think you
> should feel free to update the packages in any case.

I have written to both persons in question and had a positive response from
Phil Thompson, still waiting for Luciano's response.

> Having said all this, I strongly encourage Python Qt developers on Maemo
> to use PySide instead of PyQt. We'll be generating our future Maemo 6
> API bindings using PySide, so if you want to be able to utilize them,
> you'll need to go with PySide in any case. In addition, having only one
> set of Python Qt binding libraries on the device is probably greatly
> preferable to the end user. I understand PySide is at the moment a bit
> rough, but the situation will improve a lot by the end of the year.

PyQt can _at least_ serve as a stopgap till then, especially since people can
use the tried and true PyQt today without fearing the rough edges of PySide,
and then switch if they think PySide has reached a point where it benefits
them more. The worst case scenario is IMHO people not using *either*
(potentially giving up on development altogether), PyQt because they fear
it's abandoned, and PySide because it's just not ready for prime-time yet.

As for having two bindings, well, true, but then again, end users don't care
about GTK vs Qt and they'll have to have both in the future, just as they do
on the (Linux) desktop.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads