Comments on: PySide – Nokia-sponsored LGPL bindings to Qt http://eli.thegreenplace.net/2009/08/19/pyside-nokia-sponsored-lgpl-bindings-to-qt/ Eli Bendersky's personal website Wed, 10 Mar 2010 17:32:25 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: eliben http://eli.thegreenplace.net/2009/08/19/pyside-nokia-sponsored-lgpl-bindings-to-qt/comment-page-1/#comment-202391 eliben Wed, 02 Sep 2009 02:38:16 +0000 http://eli.thegreenplace.net/?p=1892#comment-202391 <strong>Jamie,</strong> I think you're overly pessimistic. PyQt isn't going away so soon - it will take time. Moreover, PySide will start with full API compatibility and then maybe add some Pythonic APIs. The whole process is open and rests on user participation, which makes me think it can't end up too badly for the users. I think it's in their interest to keep backwards compatibility as much as possible, and I'm confident they will. Besides, their license for PySide is very liberal, so one can always take the code and create an alternative of keep it alive if Nokia gets bored and leaves it. Jamie,

I think you’re overly pessimistic. PyQt isn’t going away so soon – it will take time. Moreover, PySide will start with full API compatibility and then maybe add some Pythonic APIs. The whole process is open and rests on user participation, which makes me think it can’t end up too badly for the users. I think it’s in their interest to keep backwards compatibility as much as possible, and I’m confident they will. Besides, their license for PySide is very liberal, so one can always take the code and create an alternative of keep it alive if Nokia gets bored and leaves it.

]]> By: Jamie http://eli.thegreenplace.net/2009/08/19/pyside-nokia-sponsored-lgpl-bindings-to-qt/comment-page-1/#comment-202263 Jamie Tue, 01 Sep 2009 18:50:04 +0000 http://eli.thegreenplace.net/?p=1892#comment-202263 This is why I will NOT be using Qt for Python. I had started teaching msyelf Python with PyQt, as I wanted a good solid GUI, and now with this it's all for naught. PySide is not ready yet, but they will kill PyQt anyway, they'll change the API (they've already promised to do it in future versions) meaning changing your code in the near future, and I look for it to be dropped in a year or two anyway (just like QTJambi was) leaving developers with no supported toolkit. Looks like I need to buy the wxpython book. Thanks for nothing Nokia. This is why I will NOT be using Qt for Python. I had started teaching msyelf Python with PyQt, as I wanted a good solid GUI, and now with this it’s all for naught. PySide is not ready yet, but they will kill PyQt anyway, they’ll change the API (they’ve already promised to do it in future versions) meaning changing your code in the near future, and I look for it to be dropped in a year or two anyway (just like QTJambi was) leaving developers with no supported toolkit. Looks like I need to buy the wxpython book. Thanks for nothing Nokia.

]]>