Originally Posted by mikecomputing

what Qt C++ API do you need to access from Python when you almost can access the most via QML? and other sutable libs in python or via pyotherside?

Originally Posted by xerxes2

For me personally not that much but porting from Pyside to Pyotherside will require a lot of work anyway. Porting from Pyside to Pyqt5 is very easy as shown below:

Pyside: https://github.com/xerxes2/panucci/b...lui/qmlmain.py

Pyqt5: https://github.com/xerxes2/panucci/b...ui/qml2main.py

As I said I'm not using much Qt stuff other than Quick but porting to Pyotherside will still, if even possible, require a lot of work. Pyqt maps 1:1 with the C++ API and is very easy to use if you already used Pyside before.

And would you care to explain why Pyotherside would use less resources than Pyqt? They're both using the same Qt libs so give some proof or it didn't happen. :P Use Pyotherside if you want but for existing Pyside apps Pyqt is the much faster way to port. Pyqt is GPL3 though so your app must use that license too or you must purchase a commercial license.

Edit: Just to clarify, porting from Pyside to Pyqt5 is basically namespace changes but porting to Pyotherside will require a complete rewrite of your gui and some more stuff. I've never used Pyotherside so someone correct me if I'm wrong.

Originally Posted by mikecomputing

THP has already pointed that out in a blog post. pyotherside does not load Qt via Python. This means it has not to lookup all Qt methods in python. Its actually other way around. Python is loaded from Qt thats atleast for now makes it alpot faster startup.

Originally Posted by mattaustin

I've just ported my "Perth Trains" app to pyotherside. It's probably a bit hacky (I struggled with knowing which data types pyotherside will handle, a list of instances didn't work, but a list of dicts apparently does), and I plan to also port to pyqt at some point (just out of self-interest, and I already use pyside for fremantle/harmattan):

https://github.com/mattaustin/freman...f675729e773f35

Originally Posted by xerxes2

That's not proof, only talk. Also what's the point of seeing the gui faster if you can't use it until the rest of your app is loaded? A hello world Pyqt5/QML takes less than 2mb on my box and I really can't see a problem with that.

Edit: Hm, that should be less than 20mb ... still not extremely much. So it probably takes "a bit" more than Pyotherside.

Edit2: If I'm counting correctly a hello world pyqt5 takes around 14mb.

Edit3: Are you supposed to use qmlscene with pyotherside? Because that will use the same amount of memory as pyqt.

I've brought down startup time of gPodder on the N9 down from ~ 12 seconds (using Python 2 and PySide) to ~ 3 seconds (using Python 3.3 and the lightweight "PyOtherSide" approach)

Originally Posted by rcolistete

As thp says in his blog article about PyOtherSide :

So it seems PyOtherSide is lighter to install and load than PyQt/PySide.

But developers want and need freedom and options. Let remember that many Python mobile developers have only some hours per week or month to develop as a hobby, so if there are tools easier to migrate (from Maemo/MeeGo/PC) to Sailfish, they will want them. Some of the Python softwares could be developed in C/C++, but then it would take more developing time and some would not be finished at all.

And please, stop saying mobile Python developers are lazy. They contributed and will contribute with a lot of free and open source softwares for Maemo, MeeGo, Sailfish, etc.

Originally Posted by mikecomputing

And btw. We definitively not need too many alternatives librarys IMHO. Especially not on embedded linux.