Re: [matplotlib-devel] closing (and opening) the user survey?
> It was me :-) > > Only a day to day user who follow matplotlib (and other famous libs) > development. I clicked on the survey thinking it was public. Anyway it was > only curiosity so if you prefer keep it secret, it's cool for me ! > > Keep the good work guys !!! > You could provide the "summary view" of the results: google doc generates this view automatically, with nice charts etc, and updates it. For people a bit curious, it's a nice way to have a quick feedback without having to run any analyses of the results or to close the survey. > > > -- > HadiM > > > On Thu, Jul 18, 2013 at 12:12 AM, Paul Ivanov wrote: > >> Hey everyone, >> >> I hope this email finds you well. I got a request today from >> someone wanting to look at the survey results. How do you feel >> about just sharing the full document? We're at 580 responses >> right now, and it's been really a slow trickle in last couple of >> weeks after the initial splash. Or we could do another round on >> twitter and G+ and say the survey will be closed at the end of >> the month, and then release the results. >> >> Thoughts? >> >> best, >> -- >>_ >> / \ >> A* \^ - >> ,./ _.`\\ / \ >> / ,--.S\/ \ >>/ `"~,_ \\ >> __o ? >>_ \<,_ /:\ >> --(_)/-(_).../ | \ >> --...J >> Paul Ivanov >> http://pirsquared.org >> >> >> -- >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> ___ >> Matplotlib-devel mailing list >> Matplotlib-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > > > > -- > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Reorganizing axes plot methods
On 07/17/2013 04:57 PM, Eric Firing wrote: > On 2013/07/17 3:14 AM, Michael Droettboom wrote: >> Yes. This is great work! >> >> Just to chime in (after having been away for most of this conversation) --> >> >> I think we can do this reorganization now without introducing any >> implicit (or otherwise) use of gca()/pyplot stuff in the Axes class >> methods. Refactoring how the pyplot wrapper is done can be done as a >> separate project at a later time (or even in parallel if someone wants >> to, since all of Nelle's work at the end of the day doesn't change the >> Axes interface). >> >> My only other comment (and I mentioned this in PR #2213 as well) is that >> having the short stub functions in the Axes class in addition to the >> actual implementations elsewhere introduces a new >> synchronization/maintenance problem between the two. Maybe it makes >> sense to merely add the implementation functions to the Axes class >> namespace dynamically. Magical, sure, but should have ultimately the >> same result as far as introspection, autocompletion and other IPython >> goodness is concerned. >> >> Mike > Mike, > > One other option is to have the new private modules include mixin > classes from which Axes would inherit methods. There would be a lot of > mixins, and this would be an example of the dreaded multiple > inheritance, but it would be simple and explicit, with no magic. > > Eric > > I think either approach is fine as far as I'm concerned, though what Eric suggests is probably a bit simpler in terms of lines of code. Mike -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] closing (and opening) the user survey?
I'm fine with that. I actually had the same idea yesterday. I don't think we'll get many more responses than we already have. I'll go ahead close the survey and then make an official announcement on the usual channels. Mike On 07/17/2013 06:12 PM, Paul Ivanov wrote: > Hey everyone, > > I hope this email finds you well. I got a request today from > someone wanting to look at the survey results. How do you feel > about just sharing the full document? We're at 580 responses > right now, and it's been really a slow trickle in last couple of > weeks after the initial splash. Or we could do another round on > twitter and G+ and say the survey will be closed at the end of > the month, and then release the results. > > Thoughts? > > best, -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Results of matplotlib user survey 2013
We have had 508 responses to the matplotlib user survey. Quite a nice turnout! You can view the results here: https://docs.google.com/spreadsheet/viewanalytics?key=0AjrPjlTMRTwTdHpQS25pcTZIRWdqX0pNckNSU01sMHc&gridId=0#chart and from there, you can access the complete raw results. I will be doing more analysis of the results over the coming days and weeks, including dedup'ing some of the responses and converting some of the free-form responses into github issues etc. Volunteers to help with this are of course welcome! Cheers, Mike -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Reorganizing axes plot methods
On 18 July 2013 15:27, Michael Droettboom wrote: > On 07/17/2013 04:57 PM, Eric Firing wrote: > > On 2013/07/17 3:14 AM, Michael Droettboom wrote: > >> Yes. This is great work! > >> > >> Just to chime in (after having been away for most of this conversation) > --> > >> > >> I think we can do this reorganization now without introducing any > >> implicit (or otherwise) use of gca()/pyplot stuff in the Axes class > >> methods. Refactoring how the pyplot wrapper is done can be done as a > >> separate project at a later time (or even in parallel if someone wants > >> to, since all of Nelle's work at the end of the day doesn't change the > >> Axes interface). > >> > >> My only other comment (and I mentioned this in PR #2213 as well) is that > >> having the short stub functions in the Axes class in addition to the > >> actual implementations elsewhere introduces a new > >> synchronization/maintenance problem between the two. Maybe it makes > >> sense to merely add the implementation functions to the Axes class > >> namespace dynamically. Magical, sure, but should have ultimately the > >> same result as far as introspection, autocompletion and other IPython > >> goodness is concerned. > >> > >> Mike > > Mike, > > > > One other option is to have the new private modules include mixin > > classes from which Axes would inherit methods. There would be a lot of > > mixins, and this would be an example of the dreaded multiple > > inheritance, but it would be simple and explicit, with no magic. > > > > Eric > > > > > I think either approach is fine as far as I'm concerned, though what > Eric suggests is probably a bit simpler in terms of lines of code. > I'm attempting an implementation of https://github.com/matplotlib/matplotlib/pull/2213 using mixins, to get my head around this idea. I'll keep you posted on the code. > > Mike > > > -- > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Results of matplotlib user survey 2013
Apologies: I didn't realize the link to the raw results only exists for users with edit permissions. The public URL for the raw results is: https://docs.google.com/spreadsheet/ccc?key=0AjrPjlTMRTwTdHpQS25pcTZIRWdqX0pNckNSU01sMHc&usp=sharing Mike On 07/18/2013 09:42 AM, Michael Droettboom wrote: We have had 508 responses to the matplotlib user survey. Quite a nice turnout! You can view the results here: https://docs.google.com/spreadsheet/viewanalytics?key=0AjrPjlTMRTwTdHpQS25pcTZIRWdqX0pNckNSU01sMHc&gridId=0#chart and from there, you can access the complete raw results. I will be doing more analysis of the results over the coming days and weeks, including dedup'ing some of the responses and converting some of the free-form responses into github issues etc. Volunteers to help with this are of course welcome! Cheers, Mike -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
