Hi,
1.0.3 packages are available for OS X.
I'll be going on vacation next week and my work project using PySide
will be winding down over the same period. It would be nice if the
PySide changes could be pulled into master before then
Thanks,
Gerald.
On 31/05/2011 5:10 PM, Gerald Storer wrote:
Hi Gerald,
thank you very much! I applied most of your changes to my matplotlib
version 1.0.1
on Windows with Python 2.6. Together with the new package of PySide I
was able to
migrate a whole project of mine from PyQt to PySide with only minimal changes.
The first test are very promissing. Even so
1.0.3 packages for Windows and Ubuntu/Debian are available to test with.
I'm not sure that the OS X package is ready yet. If you want to get
testing with it quicker jumping up and down on their mailing list
normally gets them out faster.
I also added an update to formlayout.py. I've merged in
The pyside bug affecting matplotlib pyside backend is now fixed
with pyside 1.0.3
I would be nice to have the pyside option in the next matplotlib release...
Regards,
David
Le 06/05/11 10:32, David Trémouilles a écrit :
> Hello,
>
> This is not directly related to your patch but I would like to
Based on this and some other comments I've made the minimum compatible
version 1.0.3.
Anyone wishing to test can use the nightly builds here:
http://www.pyside.org/files/nightly/ or just wait for next months
release. There's also compiling the PySide source or removing the
version check too.
I've added some comments and tested against PyQt4 4.7.3 -- I don't have
PySide installed, so I'll just assume it works there, too.
Cheers,
Mike
On 05/05/2011 09:36 PM, Gerald Storer wrote:
> Hi,
> I was wondering if I could get a comment on this. Its been 4 weeks
> since I submitted the origina
Hello,
This is not directly related to your patch but I would like to
report here that I still have at least one issue on MacOs
that prevent matplotlib to work with your pyside backend.
Indeed current PySide version (1.0.2) have a bug on MacOS that seems to
have been fixed recently:
http://bugs.p
Hi,
I was wondering if I could get a comment on this. Its been 4 weeks
since I submitted the original version and it has been more or less
production ready since Monday.
https://github.com/matplotlib/matplotlib/pull/80
Thanks,
Gerald.
On 11/04/2011 4:49 PM, Gerald Storer wrote:
> Hi,
> I've s
Hi,
I've submitted a pull request with backend changes that (should) let all
currently supported versions of PyQt work along side PySide. I've
tested with PyQt 4.8.3 and PySide 1.0.0.
I haven't bothered chasing down old versions of PyQt as they seem elusive.
Gerald.
On 29/03/2011 3:25 AM, but
Looking forward, supporting the Python 3 compatible PyQt API is likely the
way to go.
Le , Gerald Storer a écrit :
On 28/03/2011 1:10 AM, Peter Butterworth wrote:
Wouldn't it be possible to use a single backend compatible with both
PyQt and Pyside ?
The current Qt mpl backend uses t
rom: Peter Butterworth [butt...@gmail.com]
Sent: Sunday, March 27, 2011 1:10 PM
To: matplotlib-devel
Subject: Re: [matplotlib-devel] Backend for Pyside
Wouldn't it be possible to use a single backend compatible with both
PyQt and Pyside ?
Other projects (enthought, ipython, spyderlib) seem to be
Wouldn't it be possible to use a single backend compatible with both
PyQt and Pyside ?
Other projects (enthought, ipython, spyderlib) seem to be able to
handle the issue by importing from a proxy qt module that does the
right imports and handles the incompatibilities. The preferred backend
is set
It turns out that it was also trivial to get the figure options editor
working with PySide.
All that needed to be done was (in formlayout.py):
* Replace the references to PyQt with PySide
* Change: from PyQt.QtCore import (Qt, SIGNAL, SLOT, QSize, QString,
On 01/18/2011 08:13 PM, Jed Ludlow wrote:
> Please forgive me if I'm raising a heretical question with this since I
> understand the topic of competing Qt bindings for Python gets a little
> touchy in and of itself. Nonetheless, the elephant is in the room. I
> searched the archives and found only
On Tue, Jan 18, 2011 at 11:18 PM, Eric Firing wrote:
>
> 2) Interactive backends, to be fully useful, need to be be supported by
> ipython.
As long as the event loop handling of pyside is similar to pyqt's one,
it might just work already.
But even if it doesn't, from the IPython side we are *ver
On 01/18/2011 08:13 PM, Jed Ludlow wrote:
> Please forgive me if I'm raising a heretical question with this since I
> understand the topic of competing Qt bindings for Python gets a little
> touchy in and of itself. Nonetheless, the elephant is in the room. I
> searched the archives and found only
On Tue, Jan 18, 2011 at 11:13:47PM -0700, Jed Ludlow wrote:
>Please forgive me if I'm raising a heretical question with this since I
>understand the�topic of competing Qt bindings for Python gets a little
>touchy in and of itself.
>[...]
>Has there been any additional discussion
17 matches
Mail list logo
