3 Oct 23:13
Re: PyQt4 and Python 3.0
From: Andreas Pakulat <apaku <at> gmx.de>
Subject: Re: PyQt4 and Python 3.0
Newsgroups: gmane.comp.python.pyqt-pykde
Date: 2008-10-03 21:13:24 GMT
Subject: Re: PyQt4 and Python 3.0
Newsgroups: gmane.comp.python.pyqt-pykde
Date: 2008-10-03 21:13:24 GMT
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 <mark <at> qtrac.eu> 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 QString, only str, plus some static functions for things that str > > > doesn't provide, e.g., QString.simplified(s : str) -> str > > > - No QByteArray, only bytes (or bytearray) > > > - No QVariant, only object > > > - Guarantee that "from PyQt4.QtGui import *" and similar will only > > > import objects whose name begins with capital Q. > > > > That'd be cool. An alternative that I think would be even better > > would be to provide a "Qt" namespace as per QtRuby and drop the > > Q prefix from the classes, so Qt.Application, Qt.Widget, &c. > > That'd dodge the ugly namespace pollution while not causing > > much more typing. > > I like that(Continue reading)> > But how do we then distinguish QtGui.QApplication from > QtCore.QApplication? (Or does that even matter?) There's no QtCore.QApplication. It would be Qt.CoreApplication and Qt.Application.
>
> But how do we then distinguish QtGui.QApplication from
> QtCore.QApplication? (Or does that even matter?)
There's no QtCore.QApplication. It would be Qt.CoreApplication and
Qt.Application.
RSS Feed