On 2010-04-19, Matti Airas wrote:
> On 19.04.2010 16:04, ext Mark Summerfield wrote:
> > OK, then: "Adopt PyQt's API 2 for PySide on Python 3"
> >
> > (D'you want me to reissue just for the title change?)
>
> Definitely not, I can modify the document according to your
> instructions. And did.
>
> > Personally, I think that the key thing that matters here is that Python
> > programmers should not have to know or care about QVariant, so they
> > should be completely insulated from it by having automatic conversions.
> > (But with some kind of back door for when it really matters what kind of
> > object you want inside the QVariant.)
>
> Wouldn't it then be simplest to provide automatic conversions whenever
> possible but still provide QVariant as-is if explicit use is equired?
Yes. And another benefit would be that in effect this would cover both
API 1 and API 2. Code using API 1 (plus code that really needed to
specify the type) would explicitly use QVariant and code using API 2
would just ignore QVariant and use Python types directly. So best of
both worlds:-)
> (I'm getting a deja-vu about this mail, hopefully I didn't reply it
> already...)
I don't think so;-)
(Although I always get 2 copies of every mail on this list...)
--
Mark Summerfield, Qtrac Ltd, www.qtrac.eu
C++, Python, Qt, PyQt - training and consultancy
"Rapid GUI Programming with Python and Qt" - ISBN 0132354187
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
