Looking forward, supporting the Python 3 compatible PyQt API is likely the way to go.
···
Le , Gerald Storer <gds@…943…> 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 the old PyQt slots/signals API which PySide doesn’t really support (there are some macros but they don’t work 100% the same). From a quick glance at the IPython implementation it looks like they are using the new API which means older versions (<4.5) of PyQt won’t be supported. This might be ok, I don’t know.
If it isn’t then, there will need to be some try…excepts around the place or separate back ends. If you ignore the PySide bugs I had to work around I’ve only changed ~4 lines in the main backend.
Pierre’s formlayout is also using an obsolete method that isn’t present in PySide. I’ve opted to emulate it, but it would be best to change the code to use the alternative method available in both PyQt and PySide. formlayout also uses the old QString implementation of PyQt, PySide only supports the new implementation where QString is transparently convert to/from str/unicode. Setting QString = unicode seems to work though.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is likely the way to go.
Le , Gerald Storer <gds@...943...> 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 the old PyQt slots/signals API which PySide doesn't really support (there are some macros but they don't work 100% the same). From a quick glance at the IPython implementation it looks like they are using the new API which means older versions (<4.5) of PyQt won't be supported. This might be ok, I don't know.
>
> If it isn't then, there will need to be some try...excepts around the place or separate back ends. If you ignore the PySide bugs I had to work around I've only changed ~4 lines in the main backend.
>
> Pierre's formlayout is also using an obsolete method that isn't present in PySide. I've opted to emulate it, but it would be best to change the code to use the alternative method available in both PyQt and PySide. formlayout also uses the old QString implementation of PyQt, PySide only supports the new implementation where QString is transparently convert to/from str/unicode. Setting QString = unicode seems to work though.
>
> Gerald.
>
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.
Thanks,
Gerald.
···
On 11/04/2011 4:49 PM, Gerald Storer wrote:
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is likely the way to go.
Le , Gerald Storer <gds@...943...> 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 the old PyQt slots/signals API which PySide doesn't really support (there are some macros but they don't work 100% the same). From a quick glance at the IPython implementation it looks like they are using the new API which means older versions (<4.5) of PyQt won't be supported. This might be ok, I don't know.
>
> If it isn't then, there will need to be some try...excepts around the place or separate back ends. If you ignore the PySide bugs I had to work around I've only changed ~4 lines in the main backend.
>
> Pierre's formlayout is also using an obsolete method that isn't present in PySide. I've opted to emulate it, but it would be best to change the code to use the alternative method available in both PyQt and PySide. formlayout also uses the old QString implementation of PyQt, PySide only supports the new implementation where QString is transparently convert to/from str/unicode. Setting QString = unicode seems to work though.
>
> Gerald.
>
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a �crit :
···
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
Gerald.
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
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 original version and it has been more or less
production ready since Monday.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
Gerald.
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
--
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
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.
Gerald.
···
On 6/05/2011 4:32 PM, David Trémouilles wrote:
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on
macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a écrit :
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
Gerald.
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
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
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on
macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a �crit :
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
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 Pierre's latest version that validates the floats so an exception isn't thrown when a user inputs an invalid number.
Gerald.
···
On 31/05/2011 4:43 PM, David Trémouilles wrote:
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
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on
macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a écrit :
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
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 some bugs with missing icons
in connection
with py2exe are fixed now.
It would be great to have these changes in the next release of matplotlib!
Best regard,
Lars
···
On Tue, May 31, 2011 at 11:10 AM, Gerald Storer <gds@...943...> wrote:
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 Pierre's latest
version that validates the floats so an exception isn't thrown when a
user inputs an invalid number.
Gerald.
On 31/05/2011 4:43 PM, David Trémouilles wrote:
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
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on
macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a écrit :
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
Gerald.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options
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:
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 Pierre's latest
version that validates the floats so an exception isn't thrown when a
user inputs an invalid number.
Gerald.
On 31/05/2011 4:43 PM, David Trémouilles wrote:
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
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.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on
macports. I do not have time nor will to test with the latest current
pyside head.
Regards,
David
Le 06/05/11 03:36, Gerald Storer a écrit :
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.
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, butterw@...149... wrote:
Looking forward, supporting the Python 3 compatible PyQt API is
likely the way to go.
Le , Gerald Storer<gds@...943...> 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 the old PyQt slots/signals API
which PySide doesn't really support (there are some macros but they
don't work 100% the same). From a quick glance at the IPython
implementation it looks like they are using the new API which means
older versions (<4.5) of PyQt won't be supported. This might be ok, I
don't know.
If it isn't then, there will need to be some try...excepts around
the place or separate back ends. If you ignore the PySide bugs I had
to work around I've only changed ~4 lines in the main backend.
Pierre's formlayout is also using an obsolete method that isn't
present in PySide. I've opted to emulate it, but it would be best to
change the code to use the alternative method available in both PyQt
and PySide. formlayout also uses the old QString implementation of
PyQt, PySide only supports the new implementation where QString is
transparently convert to/from str/unicode. Setting QString = unicode
seems to work though.
Gerald.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net matplotlib-devel List Signup and Options