From nelle.varoquaux at gmail.com Thu Dec 1 14:20:30 2016 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Thu, 1 Dec 2016 11:20:30 -0800 Subject: [Matplotlib-devel] What's the plan for 2.0? Message-ID: Hi everyone, I was wondering if there is a plan for releasing 2.0. Most of the remaining tickets opened have proposed patches, and only one pull request (the sticky edge one) seem to need a fair amount of work. Cheers, N From tcaswell at gmail.com Thu Dec 1 14:22:36 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Thu, 01 Dec 2016 19:22:36 +0000 Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: References: Message-ID: I propose doing rc1 this weekend. Tom On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux wrote: > Hi everyone, > > I was wondering if there is a plan for releasing 2.0. Most of the > remaining tickets opened have proposed patches, and only one pull > request (the sticky edge one) seem to need a fair amount of work. > > Cheers, > N > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From juichenieder-nabb at yahoo.co.uk Thu Dec 1 20:06:18 2016 From: juichenieder-nabb at yahoo.co.uk (OceanWolf) Date: Fri, 2 Dec 2016 01:06:18 +0000 (UTC) Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: References: Message-ID: <215662638.7982092.1480640778589@mail.yahoo.com> What about the new colour cycle?? Shouldn't we wait to get the green light from Tableua before pressing forwards with an official RC?? I would hate for us to get into legal (or even just mildly unpleasant) hot-water later on because of this. Best,OceanWolf From: Thomas Caswell To: Nelle Varoquaux ; matplotlib development list Sent: Thursday, 1 December 2016, 20:22 Subject: Re: [Matplotlib-devel] What's the plan for 2.0? I propose doing rc1 this weekend. Tom On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux wrote: Hi everyone, I was wondering if there is a plan for releasing 2.0. Most of the remaining tickets opened have proposed patches, and only one pull request (the sticky edge one) seem to need a fair amount of work. Cheers, N _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From nelle.varoquaux at gmail.com Thu Dec 1 20:45:34 2016 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Thu, 1 Dec 2016 17:45:34 -0800 Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: <215662638.7982092.1480640778589@mail.yahoo.com> References: <215662638.7982092.1480640778589@mail.yahoo.com> Message-ID: > What about the new colour cycle? Shouldn't we wait to get the green light > from Tableua before pressing forwards with an official RC? I would hate for > us to get into legal (or even just mildly unpleasant) hot-water later on > because of this. If this is a blocker for the release, I'd suggest trying to find another color cycle that we'd be happy with. Cheers, N > Best, > OceanWolf > > ________________________________ > From: Thomas Caswell > To: Nelle Varoquaux ; matplotlib development list > > Sent: Thursday, 1 December 2016, 20:22 > Subject: Re: [Matplotlib-devel] What's the plan for 2.0? > > I propose doing rc1 this weekend. > > Tom > > On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux > wrote: > > Hi everyone, > > I was wondering if there is a plan for releasing 2.0. Most of the > remaining tickets opened have proposed patches, and only one pull > request (the sticky edge one) seem to need a fair amount of work. > > Cheers, > N > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > From nelle.varoquaux at gmail.com Thu Dec 1 20:47:15 2016 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Thu, 1 Dec 2016 17:47:15 -0800 Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: References: Message-ID: > I propose doing rc1 this weekend. That's great news! I look forward to it (my plots are finally going to have tick labels on them!) Cheers, N > > Tom > > On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux > wrote: >> >> Hi everyone, >> >> I was wondering if there is a plan for releasing 2.0. Most of the >> remaining tickets opened have proposed patches, and only one pull >> request (the sticky edge one) seem to need a fair amount of work. >> >> Cheers, >> N >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel From prometheus235 at gmail.com Thu Dec 1 22:30:46 2016 From: prometheus235 at gmail.com (Nick Timkovich) Date: Thu, 1 Dec 2016 21:30:46 -0600 Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: <215662638.7982092.1480640778589@mail.yahoo.com> References: <215662638.7982092.1480640778589@mail.yahoo.com> Message-ID: What's the legal problem, parula vs. viridis as per that talk ( https://www.youtube.com/watch?v=xAoljeRJ3lU)? I thought viridis was engineered independently to be perceptually uniform and was just one output of a program designed to create those palettes. Or something else entirely? On Thu, Dec 1, 2016 at 7:06 PM, OceanWolf via Matplotlib-devel < matplotlib-devel at python.org> wrote: > What about the new colour cycle? Shouldn't we wait to get the green light > from Tableua before pressing forwards with an official RC? I would hate > for us to get into legal (or even just mildly unpleasant) hot-water later > on because of this. > > Best, > OceanWolf > > ------------------------------ > *From:* Thomas Caswell > *To:* Nelle Varoquaux ; matplotlib development > list > *Sent:* Thursday, 1 December 2016, 20:22 > *Subject:* Re: [Matplotlib-devel] What's the plan for 2.0? > > I propose doing rc1 this weekend. > > Tom > > On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux > wrote: > > Hi everyone, > > I was wondering if there is a plan for releasing 2.0. Most of the > remaining tickets opened have proposed patches, and only one pull > request (the sticky edge one) seem to need a fair amount of work. > > Cheers, > N > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From juichenieder-nabb at yahoo.co.uk Thu Dec 1 22:39:42 2016 From: juichenieder-nabb at yahoo.co.uk (OceanWolf) Date: Fri, 2 Dec 2016 03:39:42 +0000 (UTC) Subject: [Matplotlib-devel] What's the plan for 2.0? In-Reply-To: References: <215662638.7982092.1480640778589@mail.yahoo.com> Message-ID: <929925577.8153031.1480649983020@mail.yahoo.com> Something else entirely ;).? Not the colourmap, but the colourcycle for lines/barcharts/etcetera... See https://github.com/matplotlib/matplotlib/issues/7248 I just feel a bit odd doing an RC which releases the code out into the public wilderness as an RC, with this issue still lingering over us... From: Nick Timkovich To: OceanWolf Cc: Thomas Caswell ; Nelle Varoquaux ; matplotlib development list Sent: Friday, 2 December 2016, 4:30 Subject: Re: [Matplotlib-devel] What's the plan for 2.0? What's the legal problem, parula vs. viridis as per that talk (https://www.youtube.com/watch?v=xAoljeRJ3lU)? I thought viridis was engineered independently to be perceptually uniform and was just one output of a program designed to create those palettes. Or something else entirely? On Thu, Dec 1, 2016 at 7:06 PM, OceanWolf via Matplotlib-devel wrote: What about the new colour cycle?? Shouldn't we wait to get the green light from Tableua before pressing forwards with an official RC?? I would hate for us to get into legal (or even just mildly unpleasant) hot-water later on because of this. Best,OceanWolf From: Thomas Caswell To: Nelle Varoquaux ; matplotlib development list Sent: Thursday, 1 December 2016, 20:22 Subject: Re: [Matplotlib-devel] What's the plan for 2.0? I propose doing rc1 this weekend. Tom On Thu, Dec 1, 2016 at 2:20 PM Nelle Varoquaux wrote: Hi everyone, I was wondering if there is a plan for releasing 2.0. Most of the remaining tickets opened have proposed patches, and only one pull request (the sticky edge one) seem to need a fair amount of work. Cheers, N ______________________________ _________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/ mailman/listinfo/matplotlib- devel ______________________________ _________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/ mailman/listinfo/matplotlib- devel ______________________________ _________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/ mailman/listinfo/matplotlib- devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sun Dec 4 23:48:33 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 05 Dec 2016 04:48:33 +0000 Subject: [Matplotlib-devel] v2.0.0rc1 is tagged Message-ID: Folks, I have just finished tagging rc1! https://github.com/matplotlib/matplotlib/releases/tag/v2.0.0rc1 Holding off on uploading to pypi and announcing to the user lists until wheels are ready for the three big platform. The wheels have been started on conda-forge. Thanks again to everyone who has worked on this. We are definitely converging! Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From nelle.varoquaux at gmail.com Sun Dec 4 23:55:19 2016 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Sun, 4 Dec 2016 20:55:19 -0800 Subject: [Matplotlib-devel] v2.0.0rc1 is tagged In-Reply-To: References: Message-ID: Yeah !!! Thanks so much for taking care of the release once again. N On Dec 4, 2016 8:48 PM, "Thomas Caswell" wrote: > Folks, > > I have just finished tagging rc1! > > https://github.com/matplotlib/matplotlib/releases/tag/v2.0.0rc1 > > Holding off on uploading to pypi and announcing to the user lists until > wheels are ready for the three big platform. The wheels have been started > on conda-forge. > > Thanks again to everyone who has worked on this. We are definitely > converging! > > Tom > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Tue Dec 6 00:38:27 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 06 Dec 2016 05:38:27 +0000 Subject: [Matplotlib-devel] [REL] matplotlib v2.0.0rc1 Message-ID: Folks, We are happy to announce matplotlib v2.0.0rc1 ! This is the first release candidate for the long awaited v2.0 release. For the full details of what is new please see http://matplotlib.org/2.0.0rc1/users/whats_new.html . Some of the highlights: - new default styles ( http://matplotlib.org/2.0.0rc1/users/dflt_style_changes.html ) - default font include most western alphabets - performance improvements in text and image rendering - vastly improved log scale ticks - many bug fixes and documentation improvements Please help us by testing the release candidate. To make this easy we have provided both wheels and conda packages for mac, linux and windows. You can install pre-releases via pip: pip install --pre matplotlib or via conda: conda install -c conda-forge/label/rc -c conda-forge matplotlib For more details see http://matplotlib.org/style_changes.html . Please report any issues to https://github.com/matplotlib/matplotlib/issues or matplotlib-users at python.org . The target for v2.0 final is around late Dec 2016/early Jan 2017. We anticipate there being at least 1 more release candidate. This release is the work of over 200 individual code contributors and many more who took part in the discussions, tested the beta releases, and reported bug reports. Thank you to everyone who contributed! Tom ps As of sending this email we are still waiting on the mac conda packages to finish building, (see https://travis-ci.org/conda-forge/matplotlib-feedstock/builds/181541792) Should be done in the next few hours, but I want to go to bed ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierre.haessig at crans.org Tue Dec 6 03:45:10 2016 From: pierre.haessig at crans.org (Pierre Haessig) Date: Tue, 6 Dec 2016 09:45:10 +0100 Subject: [Matplotlib-devel] [Matplotlib-users] [REL] matplotlib v2.0.0rc1 In-Reply-To: References: Message-ID: Hi, Le 06/12/2016 ? 06:38, Thomas Caswell a ?crit : > Some of the highlights: > > - new default styles ( > http://matplotlib.org/2.0.0rc1/users/dflt_style_changes.html ) Very nice and useful document. I just noticed that the boxplot example has a ylim issue: the boxes' height is tiny. This is a proposition to change the script (dflt_style_changes-7.py) that generate the plot: (add seeding + cut extreme outliers) np.random.seed(0) data = np.random.lognormal(size=(37, 4)) fig, (old, new) = plt.subplots(ncols=2, sharey=True) with plt.style.context('default'): new.boxplot(data, labels=['A', 'B', 'C', 'D']) new.set_title('New boxplots') with plt.style.context('classic'): old.boxplot(data, labels=['A', 'B', 'C', 'D']) old.set_title('Old boxplots') new.set_ylim(bottom=0, top=15) best, Pierre -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Tue Dec 6 11:51:54 2016 From: pmhobson at gmail.com (Paul Hobson) Date: Tue, 6 Dec 2016 08:51:54 -0800 Subject: [Matplotlib-devel] [Matplotlib-users] [REL] matplotlib v2.0.0rc1 In-Reply-To: References: Message-ID: Thanks for catching that Pierre. I think that the plot should just be log-scaled. I'll submit a PR shortly. -p On Tue, Dec 6, 2016 at 12:45 AM, Pierre Haessig wrote: > Hi, > Le 06/12/2016 ? 06:38, Thomas Caswell a ?crit : > > Some of the highlights: > > - new default styles ( http://matplotlib.org/2.0. > 0rc1/users/dflt_style_changes.html ) > > Very nice and useful document. I just noticed that the boxplot example has > a ylim issue: the boxes' height is tiny. > > This is a proposition to change the script (dflt_style_changes-7.py) that > generate the plot: > (add seeding + cut extreme outliers) > > np.random.seed(0) > > data = np.random.lognormal(size=(37, 4)) > fig, (old, new) = plt.subplots(ncols=2, sharey=True) > with plt.style.context('default'): > new.boxplot(data, labels=['A', 'B', 'C', 'D']) > new.set_title('New boxplots') > > with plt.style.context('classic'): > old.boxplot(data, labels=['A', 'B', 'C', 'D']) > old.set_title('Old boxplots') > > new.set_ylim(bottom=0, top=15) > > > best, > Pierre > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From prometheus235 at gmail.com Tue Dec 6 12:33:12 2016 From: prometheus235 at gmail.com (Nick Timkovich) Date: Tue, 6 Dec 2016 11:33:12 -0600 Subject: [Matplotlib-devel] [Matplotlib-users] [REL] matplotlib v2.0.0rc1 In-Reply-To: References: Message-ID: How permanent are Toms Temporary notes? ;) http://matplotlib.org/2.0.0rc1/users/dflt_style_changes.html#temporary-notes-tom-is-keeping-in-the-source-so-they-do-not-get-lost On Tue, Dec 6, 2016 at 10:51 AM, Paul Hobson wrote: > Thanks for catching that Pierre. I think that the plot should just be > log-scaled. I'll submit a PR shortly. > -p > > On Tue, Dec 6, 2016 at 12:45 AM, Pierre Haessig > wrote: > >> Hi, >> Le 06/12/2016 ? 06:38, Thomas Caswell a ?crit : >> >> Some of the highlights: >> >> - new default styles ( http://matplotlib.org/2.0.0rc1 >> /users/dflt_style_changes.html ) >> >> Very nice and useful document. I just noticed that the boxplot example >> has a ylim issue: the boxes' height is tiny. >> >> This is a proposition to change the script (dflt_style_changes-7.py) that >> generate the plot: >> (add seeding + cut extreme outliers) >> >> np.random.seed(0) >> >> data = np.random.lognormal(size=(37, 4)) >> fig, (old, new) = plt.subplots(ncols=2, sharey=True) >> with plt.style.context('default'): >> new.boxplot(data, labels=['A', 'B', 'C', 'D']) >> new.set_title('New boxplots') >> >> with plt.style.context('classic'): >> old.boxplot(data, labels=['A', 'B', 'C', 'D']) >> old.set_title('Old boxplots') >> >> new.set_ylim(bottom=0, top=15) >> >> >> best, >> Pierre >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sun Dec 11 16:28:27 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Sun, 11 Dec 2016 21:28:27 +0000 Subject: [Matplotlib-devel] v2.2 milestone Message-ID: Folks, As we are approaching the 2.0 release, we need to start thinking about the 2.1. Previously, I have advocated for holding 2.1 for traitlets and the GUI refactor, however given the time delays, this needs to be re-addressed. There is already a tremendous amount of work sitting on master that we need to get out to the world (for example story645's work on plotting against string-categoricals). To start organizing for this I have created a 2.2 milestone, please move any issues that you do not think should block 2.1 to 2.2. Things that you can not be done with out a major API break, please move to the 3.0 milestone. I will commit to reviewing the GUI overhaul (once 2.0 final is out) so that should stay in 2.1 (sorry oceanwolf and fariza!). There should probably be a wider discussion / rethink of how we use milestones/projects, but I think we should defer that until github's current rash of UI / PM changes settles down. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From morph at debian.org Mon Dec 12 19:52:29 2016 From: morph at debian.org (Sandro Tosi) Date: Mon, 12 Dec 2016 19:52:29 -0500 Subject: [Matplotlib-devel] v2.0.0rc1 is tagged In-Reply-To: References: Message-ID: thanks Thomas! I've uploaded the RC1 to debian experimental in order to check what's the buildability status of all those weird architectures we support and also because i would like to understand your plan about a release. Debian is about to freeze to prepare the next stable release, named stretch (we should consider the end of January as the last date i can upload a package for it to be released in stretch, but it's wiser to upload earlier to avoid any surprise) I would be totally fine to release with a RC of matplotlib if a final release wont be out by that time, but what do you think? currently we have 1.5.3 in stretch; do you think a final 2.0.0 is possible for the early Jan? thanks! On Sun, Dec 4, 2016 at 11:48 PM, Thomas Caswell wrote: > Folks, > > I have just finished tagging rc1! > > https://github.com/matplotlib/matplotlib/releases/tag/v2.0.0rc1 > > Holding off on uploading to pypi and announcing to the user lists until > wheels are ready for the three big platform. The wheels have been started > on conda-forge. > > Thanks again to everyone who has worked on this. We are definitely > converging! > > Tom > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi From tcaswell at gmail.com Mon Dec 12 20:37:58 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 13 Dec 2016 01:37:58 +0000 Subject: [Matplotlib-devel] v2.0.0rc1 is tagged In-Reply-To: References: Message-ID: The goal is late December / early January, but we have not been great about hitting those recently. I can definitely promise an rc2 with some bug fixes that got merged in the past week or so. We have gotten relatively little feedback which either means things are working fine or no one is trying out the rc. Tom On Mon, Dec 12, 2016 at 7:53 PM Sandro Tosi wrote: > thanks Thomas! > > I've uploaded the RC1 to debian experimental in order to check what's > the buildability status of all those weird architectures we support > and also because i would like to understand your plan about a release. > > Debian is about to freeze to prepare the next stable release, named > stretch (we should consider the end of January as the last date i can > upload a package for it to be released in stretch, but it's wiser to > upload earlier to avoid any surprise) > > I would be totally fine to release with a RC of matplotlib if a final > release wont be out by that time, but what do you think? currently we > have 1.5.3 in stretch; do you think a final 2.0.0 is possible for the > early Jan? > > thanks! > > On Sun, Dec 4, 2016 at 11:48 PM, Thomas Caswell > wrote: > > Folks, > > > > I have just finished tagging rc1! > > > > https://github.com/matplotlib/matplotlib/releases/tag/v2.0.0rc1 > > > > Holding off on uploading to pypi and announcing to the user lists until > > wheels are ready for the three big platform. The wheels have been > started > > on conda-forge. > > > > Thanks again to everyone who has worked on this. We are definitely > > converging! > > > > Tom > > > > _______________________________________________ > > Matplotlib-devel mailing list > > Matplotlib-devel at python.org > > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > G+: https://plus.google.com/u/0/+SandroTosi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Wed Dec 14 18:36:10 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Wed, 14 Dec 2016 23:36:10 +0000 Subject: [Matplotlib-devel] v2.0 release plans Message-ID: Folks, We have heard remarkably little back about rc1 (which is either a very good or very bad sign). I propose we do an rc2 this weekend and in addition to announcing to our lists (plus twitter) we also hit the pandas, jupyter, numpy, and scipy mailing lists. I would target a final release the first week of Jan 2017. Seems like a good way to start the new year :) Thoughts? Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Thu Dec 15 16:00:18 2016 From: ben.v.root at gmail.com (Benjamin Root) Date: Thu, 15 Dec 2016 16:00:18 -0500 Subject: [Matplotlib-devel] v2.0 release plans In-Reply-To: References: Message-ID: That should be do-able. I have no objections. On Wed, Dec 14, 2016 at 6:36 PM, Thomas Caswell wrote: > Folks, > > We have heard remarkably little back about rc1 (which is either a very > good or very bad sign). I propose we do an rc2 this weekend and in > addition to announcing to our lists (plus twitter) we also hit the pandas, > jupyter, numpy, and scipy mailing lists. > > I would target a final release the first week of Jan 2017. Seems like a > good way to start the new year :) > > Thoughts? > > Tom > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sun Dec 18 16:50:27 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Sun, 18 Dec 2016 21:50:27 +0000 Subject: [Matplotlib-devel] v2.0.0rc2 Message-ID: Folks, rc2 has been tagged an the various CI tools are spinning to build the binaries. I will upload to pypi and announce widely once they are all done. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Wed Dec 21 00:06:49 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Wed, 21 Dec 2016 05:06:49 +0000 Subject: [Matplotlib-devel] [REL] matplotlib 2.0.0rc2 Message-ID: Folks, We are happy to announce matplotlib v2.0.0rc2 ! Please re-distribute this widely. This is the final planned release candidate for the long awaited mpl v2.0 release. For the full details of what is new please see http://matplotlib.org/2.0.0rc2/users/whats_new.html Some of the highlights: - new default style (see http://matplotlib.org/2.0.0rc2/users/dflt_style_changes.html ) - new default color map (viridis) - default font includes most western alphabets - performance improvements in text and image rendering - many bug fixes and documentation improvements - many new rcparams Please help us by testing the release candidate! We would like to hear about any uses where the new defaults are significantly worse, any changes we failed to documents, or (as always) any bugs and regressions. To make this easy we have both wheels and conda packages for mac, linux and windows. You can install pre-releases via pip: pip install --pre matplotlib or via conda: conda update --all -c conda-forge conda install -c conda-forge/label/rc -c conda-forge matplotlib For more details see http://matplotlib.org/style_changes.html . Please report any issues to https://github.com/matplotlib/matplotlib/issues or matplotlib-users at python.org . The target for v2.0 final is early Jan 2017. This release is the work of over 200 individual code contributors and many more who took part in the discussions, tested the pre-releases, and reported bug reports. Thank you to everyone who contributed! Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From efiring at hawaii.edu Wed Dec 21 00:40:03 2016 From: efiring at hawaii.edu (Eric Firing) Date: Tue, 20 Dec 2016 19:40:03 -1000 Subject: [Matplotlib-devel] need wxPython reviewers for PR Message-ID: We have a PR to fix a problem in backend_wx.py, and as far as I know most of us who have been reviewing PRs recently are not WX users. Hence this call for assistance: if you use the wxagg backend, and can build matplotlib from source, please try out the patch and review it: https://github.com/matplotlib/matplotlib/pull/7652 Thanks. Eric From ndbecker2 at gmail.com Wed Dec 21 06:59:00 2016 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 21 Dec 2016 06:59 -0500 Subject: [Matplotlib-devel] [REL] matplotlib 2.0.0rc2 References: Message-ID: Thomas Caswell wrote: > Folks, > > We are happy to announce matplotlib v2.0.0rc2 ! > > Please re-distribute this widely. > > This is the final planned release candidate for the long awaited mpl v2.0 > release. > > For the full details of what is new please see > http://matplotlib.org/2.0.0rc2/users/whats_new.html > > Some of the highlights: > > - new default style (see > http://matplotlib.org/2.0.0rc2/users/dflt_style_changes.html ) > - new default color map (viridis) > - default font includes most western alphabets > - performance improvements in text and image rendering > - many bug fixes and documentation improvements > - many new rcparams > > Please help us by testing the release candidate! We would like to hear > about any uses where the new defaults are significantly worse, any changes > we failed to documents, or (as always) any bugs and regressions. > > To make this easy we have both wheels and conda packages for mac, linux > and > windows. You can install pre-releases via pip: > > pip install --pre matplotlib > > or via conda: > > conda update --all -c conda-forge > conda install -c conda-forge/label/rc -c conda-forge matplotlib > > For more details see http://matplotlib.org/style_changes.html . > > Please report any issues to > https://github.com/matplotlib/matplotlib/issues or matplotlib-users at > python.org . > > The target for v2.0 final is early Jan 2017. > > This release is the work of over 200 individual code contributors and many > more who took part in the discussions, tested the pre-releases, and > reported bug reports. > > Thank you to everyone who contributed! > > Tom > I just tried it out (pip3 install --pre --user --upgrade) and on the first try, I see a problem. In the attached, each plot has a marker, but the markers aren't shown in the legend for 2 of the lines. -------------- next part -------------- A non-text attachment was scrubbed... Name: figure1.pdf Type: application/pdf Size: 19998 bytes Desc: not available URL: From ndbecker2 at gmail.com Wed Dec 21 07:00:15 2016 From: ndbecker2 at gmail.com (Neal Becker) Date: Wed, 21 Dec 2016 07:00:15 -0500 Subject: [Matplotlib-devel] [REL] matplotlib 2.0.0rc2 References: Message-ID: Neal Becker wrote: ... https://github.com/matplotlib/matplotlib/issues/7653 From tcaswell at gmail.com Thu Dec 29 18:27:29 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Thu, 29 Dec 2016 23:27:29 +0000 Subject: [Matplotlib-devel] jupyter code of conduct Message-ID: Folks, Jupyter is working on finalizing a code of conduct: https://github.com/jupyter/governance/pull/23 I will likely suggest we adopt the same document (after they have some time to work out the kinks) in 6-9mo time frame. Please have a look at it and bring up any concerns now so they can be worked through with the jupyter folks in the loop. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: