[PyKDE] QString in PyQt4 - Request for Comments

Jim Bublitz jbublitz at nwinternet.com
Tue Oct 18 19:47:00 BST 2005


On Tuesday 18 October 2005 10:24, Phil Thompson wrote:
> I'm wondering whether QString should be dropped in PyQt4 in order to make
> it more Pythonic.
>
> At the moment Python strings and unicode strings are automatically
> converted to QStrings when passed as arguments - so there would be no
> change there. If a QString was returned by a method or an operator then a
> unicode string would be returned instead.
>
> Obviously you would lose all of QString's methods and would have to rely on
> what Python gives you for manipulating strings.
>
> One of the limitations of QString has been that you couldn't do...
>
> q = "Py" + QString("Qt")
>
> ...but with current snapshots you can - so this is an argument for keeping
> QString as it has become easier to use.
>
> BTW, the following is a consequence of the additional support...
>
> s = "Py"
> # s is of type str
> s += QString("Qt")
> # s is now of type QString
>
> Comments, opinions welcome.

KDE has a lot of template code using QString, as well as DCOP calls that take 
or return QString. As long as it's possible to handle those, I wouldn't 
object. I do like the correspondence between the C++ and Python APIs, but 
that isn't a huge deal.

Jim




More information about the PyQt mailing list