Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Michael Droettboom
On 07/22/2013 10:42 AM, Nathaniel Smith wrote: > On Mon, Jul 22, 2013 at 2:55 PM, Michael Droettboom wrote: >> This is why I suggested that the best way forward is to implement some sort >> of easy styling functionality (like what Tony Yu has submitted in #2236, >> though I haven't had a chance to

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Nathaniel Smith
On Mon, Jul 22, 2013 at 2:55 PM, Michael Droettboom wrote: > This is why I suggested that the best way forward is to implement some sort > of easy styling functionality (like what Tony Yu has submitted in #2236, > though I haven't had a chance to look at it yet), and make it explicit for > the use

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Michael Droettboom
On 07/22/2013 11:34 AM, Chris Beaumont wrote: I had the same question about opt-out vs opt-in. Personally, I vote for opt-out. I would like to see each release of MPL have an associated style (which may be the same as the last release, but maybe not). With Tony's style PR, users that need const

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Chris Beaumont
I had the same question about opt-out vs opt-in. Personally, I vote for opt-out. I would like to see each release of MPL have an associated style (which may be the same as the last release, but maybe not). With Tony's style PR, users that need constant styles would either put `style.use('1.3')` in

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Nathaniel Smith
On Sun, Jul 21, 2013 at 2:48 AM, Chris Beaumont wrote: > I don't fully agree with Eric that changing the defaults should be treated > as an API break -- yes, it may irritate a minority of users, but their code > will still run. I'd flip around your argument for the role of rcParams and > customiza

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-22 Thread Michael Droettboom
On 07/20/2013 09:07 PM, Eric Firing wrote: > On 2013/07/20 2:38 PM, David P. Sanders wrote: >> And this is my problem with 'rc': it brings to mind an arcane config >> file hidden away somewhere that has a terrible syntax and must not be >> touched. >> >> As Chris and Adrian have emphasized, the po

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-21 Thread Tony Yu
On Sat, Jul 20, 2013 at 9:10 PM, David P. Sanders < dpsand...@ciencias.unam.mx> wrote: > > > > On Sat, Jul 20, 2013 at 8:48 PM, Chris Beaumont wrote: > >> >> > However, default tweaking need not be painful. As has been mentioned, a >> first step would be an easier way to change a whole set of

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Kevin Davies
Regarding whole sets of rcParams, you may want to look at this: https://github.com/tonysyu/mpltools Kevin On 07/20/2013 09:48 PM, Chris Beaumont wrote: 'image.cmap' -- nice! Shows how much I know :) I don't fully

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread David P. Sanders
On Sat, Jul 20, 2013 at 8:48 PM, Chris Beaumont wrote: > 'image.cmap' -- nice! Shows how much I know :) > > I don't fully agree with Eric that changing the defaults should be treated > as an API break -- yes, it may irritate a minority of users, but their code > will still run. I'd flip around yo

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Chris Beaumont
'image.cmap' -- nice! Shows how much I know :) I don't fully agree with Eric that changing the defaults should be treated as an API break -- yes, it may irritate a minority of users, but their code will still run. I'd flip around your argument for the role of rcParams and customization: the majori

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Tony Yu
On Sat, Jul 20, 2013 at 4:47 PM, Chris Beaumont wrote: > Hi, > > I thought I'd chime in on this discussion -- Adrian Price-Whelan and I put > together plotornot during the SciPy sprints. > > I wouldn't advocate for linking to plotornot from matplotlib -- the idea > is semi tongue-in-cheek, and me

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Eric Firing
On 2013/07/20 2:38 PM, David P. Sanders wrote: > And this is my problem with 'rc': it brings to mind an arcane config > file hidden away somewhere that has a terrible syntax and must not be > touched. > > As Chris and Adrian have emphasized, the point is that we *should* be > tweaking away at the

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Eric Firing
On 2013/07/20 11:47 AM, Chris Beaumont wrote: > Hi, > > I thought I'd chime in on this discussion -- Adrian Price-Whelan and I > put together plotornot during the SciPy sprints. > > I wouldn't advocate for linking to plotornot from matplotlib -- the idea > is semi tongue-in-cheek, and meant to gaug

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Adrian Price-Whelan
t; >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Matplotlib-devel digest..." >> >> >> Today's Topics: >> >> 1. Re: Plot or Not: voting to create better matplotlibrc >> (Eric Firing) >>2. Re: How

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Chris Beaumont
gt; https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > > > -- > > Message: 2 > Date: Sat, 20 Jul 2013 08:55:37 -1000 > From: Eric Firing > Subject: Re: [matplotlib-devel] How to use STIX fonts in matplotlib >

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Eric Firing
On 2013/07/20 8:58 AM, Benjamin Root wrote: > From discussions with others at SciPy, we found ourselves disagreeing > on what default we would want. We also weren't sure exactly which params > were the ones that people tended to change. We have zero data on this. > This site is intended to help st

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Benjamin Root
>From discussions with others at SciPy, we found ourselves disagreeing on what default we would want. We also weren't sure exactly which params were the ones that people tended to change. We have zero data on this. This site is intended to help start that data collection process. We can certainly

Re: [matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread Eric Firing
On 2013/07/20 4:18 AM, David P. Sanders wrote: > Hi, > > Probably many of you know about "Plot or Not", a site where we vote on > the same plot presented in different ways, to get feedback about better > matplotlibrc params: > > http://warm-escarpment-9042.herokuapp.com/ > > It seems to me an absol

[matplotlib-devel] Plot or Not: voting to create better matplotlibrc

2013-07-20 Thread David P. Sanders
Hi, Probably many of you know about "Plot or Not", a site where we vote on the same plot presented in different ways, to get feedback about better matplotlibrc params: http://warm-escarpment-9042.herokuapp.com/ It seems to me an absolutely fantastic idea! I think many people do not realise how f