Re: [matplotlib-devel] Backend for Pyside
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. >> >> https://github.com/matplotlib/matplotlib/pull/80 >> >> 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, butt...@gmail.com wrote: 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 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 >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- 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 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Backend for Pyside
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. >>> >>> https://github.com/matplotlib/matplotlib/pull/80 >>> >>> 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, butt...@gmail.com wrote: > 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 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 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Backend for Pyside
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 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 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. https://github.com/matplotlib/matplotlib/pull/80 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, butt...@gmail.com wrote: >> 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 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 > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- 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
[matplotlib-devel] bug in plot_basedir and changed default directory in plot_directive?
It seems that this commit [1] changed the default directory for the sphinx plots directory (now needs to be alongside the directive and not in the directory above it?) and now our project's docs will not build across different versions of matplotlib without some magic. So I tried setting from os.path import dirname, abspath plot_basedir = dirname(dirname(abspath(__file__))) in our sphinx conf.py. We have source/conf.py and plots/ is in the parent directory of source for the directive plot:: plots/some_file.py. However, now I get this error [2] and this traceback [3]. It seems the build/plot_directive folder is created before a subsequent call to os.makedir. If I move plots to its expected default location and then set the plot_basedir manually it's fine. Is this a bug or user error? Is there some reason our plots directory can't be in the parent directory of source? [1] https://github.com/matplotlib/matplotlib/commit/a205f5460f13d47aa5b5fad662005c382dd096ee [2] http://pastebin.com/KQp11CiS [3] http://pastebin.com/4LY1Pt1Q Skipper -- 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 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] bug in pyplot.subplot if squeeze is False
I filed a bug report here [1]. If squeeze is false, ret never gets defined. https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/pyplot.py#L794 Skipper [1] https://sourceforge.net/tracker/?func=detail&aid=3309967&group_id=80706&atid=560720 PS. Should I ping the user or devel list with bug reports (or neither)? -- 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 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] [pystatsmodels] matplotlib/sphinxext problems for VAR plots in the docs
On Tue, May 31, 2011 at 8:31 PM, Skipper Seabold wrote: > FYI, our docs won't build with matplotlib after this commit [1]. It > expects the plots dir to be in the same directory as the plot > directive by default. My attempts to define plot_basedir in conf.py > did not work. I pinged the mpl devel list for any pointers. I also > filed a bug reports for squeeze == False in pyplot.subplot (though I > think it'd be easier if we just set squeeze = True for now since it > don't think it really matters all that much). > > Skipper > > [1] > https://github.com/matplotlib/matplotlib/commit/a205f5460f13d47aa5b5fad662005c382dd096ee > Forwarding to the mpl devel list. JDH -- 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 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
