[IPython-dev] [Enthought-Dev] PySide to replace PyQt?
Wed Aug 26 18:11:24 CDT 2009
This was heavily discussed at the conference last week.
It seems as though Phil Thompson might have painted himself into a
corner. At any rate, I for one welcome our new Finnish overlords.
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:
>> 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
> 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
> 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
> release. To import PySide you have to use “import PySide” instead
> of “import
> I didn't know where to post this. PySide needs to mature a bit
> 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
> 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
> Glenn H. Tarbox, PhD || 206-274-6919
> Enthought-Dev mailing list
More information about the IPython-dev