[IPython-dev] [Enthought-Dev] PySide to replace PyQt?

Darren Dale dsdale24 at gmail.com
Thu Aug 27 07:49:52 EDT 2009

Hi David,

On Wed, Aug 26, 2009 at 7:11 PM, David Warde-Farley<dwf at cs.toronto.edu> wrote:
> This was heavily discussed at the conference last week.
> It seems as though Phil Thompson might have painted himself into a
> corner.

I don't know. Who could have anticipated the sale of Qt and subsequent
license change by Nokia?

> At any rate, I for one welcome our new Finnish overlords.

I'll reserve judgment until they can build and distribute a stable
product across platforms.


> On 25-Aug-09, at 11:31 PM, Glenn Tarbox, PhD wrote:
>> Sooner or later, something was gonna need to happen WRT Riverbank
>> and the
>> PyQt licensing.  I had hoped that an entirely new project wasn't
>> going to be
>> necessary.... but apparently it is.
>> PySide Released to the Wild:
>> http://labs.trolltech.com/blogs/2009/08/25/pyside-released-to-the-
>> wild/
>>> From the PySide FAQ
>> What about PyQt?
>> Nokia’s initial research into Python bindings for Qt involved
>> speaking with
>> Riverbank Computing, the makers of PyQt. We had several discussions
>> with
>> them to see if it was possible to use PyQt to achieve our goals.
>> Unfortunately, a common agreement could not be found , so in the end
>> we
>> decided to proceed with PySide.
>> We will however maintain API compatibility with PyQt (you can use
>> the same
>> method names but can’t inter-operate with PyQt), at least for the
>> initial
>> release. To import PySide you have to use “import PySide” instead
>> of “import
>> PyQt4″.
>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>> I didn't know where to post this.  PySide needs to mature a bit
>> (support
>> more than Linux for example) but both Matplotlib and Enthought are
>> affected.  PyQt will likely need to be replaced in both packages
>> once PySide
>> becomes more mature as the licensing of PyQt is problematic now that
>> Qt is
>> LGPL.  Its also likely that with Nokia's backing, the PySide API will
>> eventually dominate.
>> Hopefully, the above statement regarding the similarity of the API
>> will make
>> moving over easy.  Personally I'd like to see a focus on Qt vs Wx by
>> Enthought as I believe it to be much more powerful... but thats my
>> personal
>> opinion and what I use.
>> As a side note, I've successfully nailed my C++ Qt code to IPython
>> using a
>> Cython shim.  The PyQt event loop is available and all seems to work
>> great.
>> -glenn
>> --
>> Glenn H. Tarbox, PhD ||  206-274-6919
>> http://www.tarbox.org
>> _______________________________________________
>> Enthought-Dev mailing list
>> Enthought-Dev at enthought.com
>> https://mail.enthought.com/mailman/listinfo/enthought-dev
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev

"In our description of nature, the purpose is not to disclose the real
essence of the phenomena but only to track down, so far as it is
possible, relations between the manifold aspects of our experience" -
Niels Bohr

"It is a bad habit of physicists to take their most successful
abstractions to be real properties of our world." - N. David Mermin

"Once we have granted that any physical theory is essentially only a
model for the world of experience, we must renounce all hope of
finding anything like the correct theory ... simply because the
totality of experience is never accessible to us." - Hugh Everett III

More information about the IPython-dev mailing list