On Wednesday 14 April 2010 07:04:56 pm detlev wrote: > > No QByteArray, QString, or QVariant > > QByteArray is still available. It was discussed (at least between Phil and > myself) but the decision was to not break compatibility again, which I > appreciated much. It saved me a lot of porting work for the eric5 > development environment. Based on my experience it isn't possible to get rid of QByteArray in language bindings. It was originally marshalled to and from a Ruby String in QtRuby, but that caused too many problems and I changed it to use QByteArray as a normal class instead of special casing it. Quite a few of the Qt apis depend on you passing a QByteArray as an initialiisation step, the QByteArray is then updated internally in the Qt libs, and then later you are expected to be able to use the updated version. If you convert the QByteArray to a python string at the initialization stage, then that sort of thing won't work.
-- Richard _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
