From pi at berkeley.edu Sun Jul 1 00:24:28 2018 From: pi at berkeley.edu (Paul Ivanov) Date: Sat, 30 Jun 2018 21:24:28 -0700 Subject: [Matplotlib-devel] moving tutorial to matplotlib org In-Reply-To: References: Message-ID: I'll protest loudly if you don't ;) Go for it and do the easy thing first and move the repo. (Also hi all, missed you, even those I don't know - trying to get back into the swing of things here) On Thu, Jun 28, 2018 at 1:58 PM, Thomas Caswell wrote: > Ben Root has also presented this (sorry Ben!). > > Tom > > On Thu, Jun 28, 2018 at 3:56 PM Thomas Caswell wrote: > >> Folks, >> >> Any protests to moving >> >> https://github.com/tacaswell/interactive_mpl_tutorial >> >> into the Matplotlib org (and renaming 'interactive_tutorial')? >> >> I have now presented a version of this 3 times and it seems well received. >> >> Another option would be to move all of that content directly into the >> docs (but is obviously a lot more work!). >> >> Tom >> > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S \/ \ / `"~,_ \ \ __o ? _ \<,_ /:\ --(_)/-(_)----.../ | \ --------------.......J Paul Ivanov http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pi at berkeley.edu Sun Jul 1 00:27:27 2018 From: pi at berkeley.edu (Paul Ivanov) Date: Sat, 30 Jun 2018 21:27:27 -0700 Subject: [Matplotlib-devel] Employer support of Matplotlib work In-Reply-To: References: Message-ID: Hi Tom, yes, I have explicit permission without a dedicated time percentage. I will now make an effort to make that a non-zero percentage. best, pi On Tue, Jun 12, 2018 at 10:15 AM, Thomas Caswell wrote: > Folks, > > Does anyone have dedicated time or explicit permission to work on > Matplotlib as part of your employment (I have 10%)? > > Feel free to respond to just me if you are not comfortable posting this > publicly. > > Tom > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S \/ \ / `"~,_ \ \ __o ? _ \<,_ /:\ --(_)/-(_)----.../ | \ --------------.......J Paul Ivanov http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Sun Jul 1 12:46:46 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Sun, 1 Jul 2018 12:46:46 -0400 Subject: [Matplotlib-devel] Employer support of Matplotlib work In-Reply-To: References: Message-ID: I have explicit permission to submit patches for bugs I discover in any open-source project I use in the course of doing my work. My employer would rather to have the patches upstream than manage them ourselves. They also encourage me to actively participate in the SciPy community. No dedicated work-level percentage though. Ben Root On Sun, Jul 1, 2018 at 12:27 AM, Paul Ivanov wrote: > Hi Tom, > > yes, I have explicit permission without a dedicated time percentage. I > will now make an effort to make that a non-zero percentage. > > best, > pi > > On Tue, Jun 12, 2018 at 10:15 AM, Thomas Caswell > wrote: > >> Folks, >> >> Does anyone have dedicated time or explicit permission to work on >> Matplotlib as part of your employment (I have 10%)? >> >> Feel free to respond to just me if you are not comfortable posting this >> publicly. >> >> Tom >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > > > -- > _ > / \ > A* \^ - > ,./ _.`\\ / \ > / ,--.S \/ \ > / `"~,_ \ \ > __o ? > _ \<,_ /:\ > --(_)/-(_)----.../ | \ > --------------.......J > Paul Ivanov > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > > _______________________________________________ > 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 jklymak at uvic.ca Sun Jul 1 13:05:30 2018 From: jklymak at uvic.ca (Jody Klymak) Date: Sun, 1 Jul 2018 10:05:30 -0700 Subject: [Matplotlib-devel] Employer support of Matplotlib work In-Reply-To: References: Message-ID: <49071B6F-842E-4A45-9BD4-0A46149F6DB0@uvic.ca> I have an academic job, and 20% is expected to be ?service?, which helping w/ matplotlib would be considered a part of. Of course I?d never get away with claiming it was the whole 20% (supposed to include internal service, and academic service), but if I were to assign 5% to it, they?d be OK w/ that. The rest is voluntary. Cheers, Jody > On Jul 1, 2018, at 9:46 AM, Benjamin Root wrote: > > I have explicit permission to submit patches for bugs I discover in any open-source project I use in the course of doing my work. My employer would rather to have the patches upstream than manage them ourselves. They also encourage me to actively participate in the SciPy community. No dedicated work-level percentage though. > > Ben Root > > On Sun, Jul 1, 2018 at 12:27 AM, Paul Ivanov > wrote: > Hi Tom, > > yes, I have explicit permission without a dedicated time percentage. I will now make an effort to make that a non-zero percentage. > > best, > pi > > On Tue, Jun 12, 2018 at 10:15 AM, Thomas Caswell > wrote: > Folks, > > Does anyone have dedicated time or explicit permission to work on Matplotlib as part of your employment (I have 10%)? > > Feel free to respond to just me if you are not comfortable posting this publicly. > > Tom > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > > -- > _ > / \ > A* \^ - > ,./ _.`\\ / \ > / ,--.S \/ \ > / `"~,_ \ \ > __o ? > _ \<,_ /:\ > --(_)/-(_)----.../ | \ > --------------.......J > Paul Ivanov > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > > _______________________________________________ > 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 efiring at hawaii.edu Mon Jul 2 17:17:28 2018 From: efiring at hawaii.edu (Eric Firing) Date: Mon, 2 Jul 2018 17:17:28 -0400 Subject: [Matplotlib-devel] Travis failure related to qt Message-ID: Does anyone understand why Travis is failing? https://github.com/matplotlib/matplotlib/pull/11412 Thanks. Eric From jklymak at uvic.ca Mon Jul 2 17:32:41 2018 From: jklymak at uvic.ca (Jody Klymak) Date: Mon, 2 Jul 2018 14:32:41 -0700 Subject: [Matplotlib-devel] Travis failure related to qt In-Reply-To: References: Message-ID: <584AF99D-1C3A-45D4-B518-6A5DB84AEA21@uvic.ca> No, but crossref: https://github.com/matplotlib/matplotlib/issues/11554 > On Jul 2, 2018, at 14:17 PM, Eric Firing wrote: > > Does anyone understand why Travis is failing? > https://github.com/matplotlib/matplotlib/pull/11412 > > Thanks. > Eric > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel From matthew.brett at gmail.com Tue Jul 3 10:08:30 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 3 Jul 2018 15:08:30 +0100 Subject: [Matplotlib-devel] Windows wheels for Python 3.7? Message-ID: Hi, What is the current procedure for generating Windows wheels? As y'all probably know, Python 3.7 came out a few days ago, and we really need to get a 3.7 wheel out ASAP to help other projects that depend on Matplotlib. I have done / am doing this for Linux / macOS - but what should happen next to get wheels for Windows? Cheers, Matthew From f.faccenda86 at gmail.com Thu Jul 5 08:37:29 2018 From: f.faccenda86 at gmail.com (Francesco Faccenda) Date: Thu, 5 Jul 2018 14:37:29 +0200 Subject: [Matplotlib-devel] Cairo backends and OpenGL use Message-ID: Dear all, I am writing to you because of an issue regarding the use of OpenGL in cairo backends from matplotlib. As I set a cairo backend with the instruction matplotlib.Use(?WXCairo?), there is evidence that the graphic computation is not being carried out by the graphic card. Since the significative amount of plotted data, the chart are heavy and slow when the user is interacting with them, so a graphic acceleration would be really appreciated. As a side note, I am embedding matplotlib canvas on wxPython stages, that?s why I choose WXCairo as backend, at first. However, setting other backends (GTKCario, TKCairo, Qt4Cairo, Qt5Cairo etc) while still using wx, still provides a working code without any errors, even if the graphic card is still not exploited. Is this an actual malfunction or am I missing something? What should I do to run matplotlib graphic computation on a graphic card? Thank you in advance. Best regards, Francesco Faccenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.barker at noaa.gov Fri Jul 6 18:21:29 2018 From: chris.barker at noaa.gov (Chris Barker - NOAA Federal) Date: Fri, 6 Jul 2018 15:21:29 -0700 Subject: [Matplotlib-devel] [matplotlib-devel] Cairo backends and OpenGL use In-Reply-To: References: Message-ID: MPL does not have a backend that used ?real? GPU rendering. And it?s very hard to make one, due to the really low level nature of OpenGL and similar APIs, and MPL?s rendering model. You might try VisPy ? it was designed for OpenGL from the start. -CHB Sent from my iPhone On Jul 5, 2018, at 5:37 AM, Francesco Faccenda wrote: Dear all, I am writing to you because of an issue regarding the use of OpenGL in cairo backends from matplotlib. As I set a cairo backend with the instruction matplotlib.Use(?WXCairo?), there is evidence that the graphic computation is not being carried out by the graphic card. Since the significative amount of plotted data, the chart are heavy and slow when the user is interacting with them, so a graphic acceleration would be really appreciated. As a side note, I am embedding matplotlib canvas on wxPython stages, that?s why I choose WXCairo as backend, at first. However, setting other backends (GTKCario, TKCairo, Qt4Cairo, Qt5Cairo etc) while still using wx, still provides a working code without any errors, even if the graphic card is still not exploited. Is this an actual malfunction or am I missing something? What should I do to run matplotlib graphic computation on a graphic card? Thank you in advance. Best regards, Francesco Faccenda ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat Jul 7 16:47:47 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 7 Jul 2018 16:47:47 -0400 Subject: [Matplotlib-devel] MPL 3.0 feature freeze Message-ID: Folks, I propose a feature-freeze for Matplotlib for tomorrow (sorry for the poor planning / communication). Open PRs which are not bug fixes and not marked as critical will be moved to the 3.1 milestone tomorrow (Sunday July 8, 2018). Goal is to finish up the RC in time for the scipy sprints next week. Any protests? Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Sat Jul 7 23:08:39 2018 From: pmhobson at gmail.com (Paul Hobson) Date: Sat, 7 Jul 2018 20:08:39 -0700 Subject: [Matplotlib-devel] MPL 3.0 feature freeze In-Reply-To: References: Message-ID: I'm in favor. Thanks for keeping us moving forward on this. On Sat, Jul 7, 2018 at 1:48 PM Thomas Caswell wrote: > Folks, > > I propose a feature-freeze for Matplotlib for tomorrow (sorry for the poor > planning / communication). Open PRs which are not bug fixes and not marked > as critical will be moved to the 3.1 milestone tomorrow (Sunday July 8, > 2018). > > Goal is to finish up the RC in time for the scipy sprints next week. > > Any protests? > > 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 Mon Jul 9 09:24:36 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 9 Jul 2018 09:24:36 -0400 Subject: [Matplotlib-devel] moving tutorial to matplotlib org In-Reply-To: References: Message-ID: Done, the material now lives at https://github.com/matplotlib/interactive_tutorial Tom On Sun, Jul 1, 2018 at 12:24 AM Paul Ivanov wrote: > I'll protest loudly if you don't ;) > > Go for it and do the easy thing first and move the repo. > > (Also hi all, missed you, even those I don't know - trying to get back > into the swing of things here) > > On Thu, Jun 28, 2018 at 1:58 PM, Thomas Caswell > wrote: > >> Ben Root has also presented this (sorry Ben!). >> >> Tom >> >> On Thu, Jun 28, 2018 at 3:56 PM Thomas Caswell >> wrote: >> >>> Folks, >>> >>> Any protests to moving >>> >>> https://github.com/tacaswell/interactive_mpl_tutorial >>> >>> into the Matplotlib org (and renaming 'interactive_tutorial')? >>> >>> I have now presented a version of this 3 times and it seems well >>> received. >>> >>> Another option would be to move all of that content directly into the >>> docs (but is obviously a lot more work!). >>> >>> Tom >>> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > > > -- > _ > / \ > A* \^ - > ,./ _.`\\ / \ > / ,--.S \/ \ > / `"~,_ \ \ > __o ? > _ \<,_ /:\ > --(_)/-(_)----.../ | \ > --------------.......J > Paul Ivanov > http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 > _______________________________________________ > 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 ben.v.root at gmail.com Mon Jul 9 10:22:56 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 9 Jul 2018 10:22:56 -0400 Subject: [Matplotlib-devel] moving tutorial to matplotlib org In-Reply-To: References: Message-ID: at some point, do we want to merge my changes that I did last year, or have you already incorporated those changes (or done something different?) On Mon, Jul 9, 2018 at 9:24 AM, Thomas Caswell wrote: > Done, the material now lives at https://github.com/matplotlib/interactive_ > tutorial > > Tom > > On Sun, Jul 1, 2018 at 12:24 AM Paul Ivanov wrote: > >> I'll protest loudly if you don't ;) >> >> Go for it and do the easy thing first and move the repo. >> >> (Also hi all, missed you, even those I don't know - trying to get back >> into the swing of things here) >> >> On Thu, Jun 28, 2018 at 1:58 PM, Thomas Caswell >> wrote: >> >>> Ben Root has also presented this (sorry Ben!). >>> >>> Tom >>> >>> On Thu, Jun 28, 2018 at 3:56 PM Thomas Caswell >>> wrote: >>> >>>> Folks, >>>> >>>> Any protests to moving >>>> >>>> https://github.com/tacaswell/interactive_mpl_tutorial >>>> >>>> into the Matplotlib org (and renaming 'interactive_tutorial')? >>>> >>>> I have now presented a version of this 3 times and it seems well >>>> received. >>>> >>>> Another option would be to move all of that content directly into the >>>> docs (but is obviously a lot more work!). >>>> >>>> Tom >>>> >>> >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Matplotlib-devel at python.org >>> https://mail.python.org/mailman/listinfo/matplotlib-devel >>> >>> >> >> >> -- >> _ >> / \ >> A* \^ - >> ,./ _.`\\ / \ >> / ,--.S \/ \ >> / `"~,_ \ \ >> __o ? >> _ \<,_ /:\ >> --(_)/-(_)----.../ | \ >> --------------.......J >> Paul Ivanov >> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 >> _______________________________________________ >> 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 Mon Jul 9 13:23:47 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 9 Jul 2018 13:23:47 -0400 Subject: [Matplotlib-devel] moving tutorial to matplotlib org In-Reply-To: References: Message-ID: There are 3 commits from you from last year, did you have more changes? Tom On Mon, Jul 9, 2018 at 10:23 AM Benjamin Root wrote: > at some point, do we want to merge my changes that I did last year, or > have you already incorporated those changes (or done something different?) > > On Mon, Jul 9, 2018 at 9:24 AM, Thomas Caswell wrote: > >> Done, the material now lives at >> https://github.com/matplotlib/interactive_tutorial >> >> Tom >> >> On Sun, Jul 1, 2018 at 12:24 AM Paul Ivanov wrote: >> >>> I'll protest loudly if you don't ;) >>> >>> Go for it and do the easy thing first and move the repo. >>> >>> (Also hi all, missed you, even those I don't know - trying to get back >>> into the swing of things here) >>> >>> On Thu, Jun 28, 2018 at 1:58 PM, Thomas Caswell >>> wrote: >>> >>>> Ben Root has also presented this (sorry Ben!). >>>> >>>> Tom >>>> >>>> On Thu, Jun 28, 2018 at 3:56 PM Thomas Caswell >>>> wrote: >>>> >>>>> Folks, >>>>> >>>>> Any protests to moving >>>>> >>>>> https://github.com/tacaswell/interactive_mpl_tutorial >>>>> >>>>> into the Matplotlib org (and renaming 'interactive_tutorial')? >>>>> >>>>> I have now presented a version of this 3 times and it seems well >>>>> received. >>>>> >>>>> Another option would be to move all of that content directly into the >>>>> docs (but is obviously a lot more work!). >>>>> >>>>> Tom >>>>> >>>> >>>> _______________________________________________ >>>> Matplotlib-devel mailing list >>>> Matplotlib-devel at python.org >>>> https://mail.python.org/mailman/listinfo/matplotlib-devel >>>> >>>> >>> >>> >>> -- >>> _ >>> / \ >>> A* \^ - >>> ,./ _.`\\ / \ >>> / ,--.S \/ \ >>> / `"~,_ \ \ >>> __o ? >>> _ \<,_ /:\ >>> --(_)/-(_)----.../ | \ >>> --------------.......J >>> Paul Ivanov >>> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 >>> _______________________________________________ >>> 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 ben.v.root at gmail.com Mon Jul 9 14:48:26 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 9 Jul 2018 14:48:26 -0400 Subject: [Matplotlib-devel] moving tutorial to matplotlib org In-Reply-To: References: Message-ID: no, that seems about right, I'll double-check later this week after tutorials are complete On Mon, Jul 9, 2018 at 1:23 PM, Thomas Caswell wrote: > There are 3 commits from you from last year, did you have more changes? > > Tom > > On Mon, Jul 9, 2018 at 10:23 AM Benjamin Root > wrote: > >> at some point, do we want to merge my changes that I did last year, or >> have you already incorporated those changes (or done something different?) >> >> On Mon, Jul 9, 2018 at 9:24 AM, Thomas Caswell >> wrote: >> >>> Done, the material now lives at https://github.com/ >>> matplotlib/interactive_tutorial >>> >>> Tom >>> >>> On Sun, Jul 1, 2018 at 12:24 AM Paul Ivanov wrote: >>> >>>> I'll protest loudly if you don't ;) >>>> >>>> Go for it and do the easy thing first and move the repo. >>>> >>>> (Also hi all, missed you, even those I don't know - trying to get back >>>> into the swing of things here) >>>> >>>> On Thu, Jun 28, 2018 at 1:58 PM, Thomas Caswell >>>> wrote: >>>> >>>>> Ben Root has also presented this (sorry Ben!). >>>>> >>>>> Tom >>>>> >>>>> On Thu, Jun 28, 2018 at 3:56 PM Thomas Caswell >>>>> wrote: >>>>> >>>>>> Folks, >>>>>> >>>>>> Any protests to moving >>>>>> >>>>>> https://github.com/tacaswell/interactive_mpl_tutorial >>>>>> >>>>>> into the Matplotlib org (and renaming 'interactive_tutorial')? >>>>>> >>>>>> I have now presented a version of this 3 times and it seems well >>>>>> received. >>>>>> >>>>>> Another option would be to move all of that content directly into the >>>>>> docs (but is obviously a lot more work!). >>>>>> >>>>>> Tom >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Matplotlib-devel mailing list >>>>> Matplotlib-devel at python.org >>>>> https://mail.python.org/mailman/listinfo/matplotlib-devel >>>>> >>>>> >>>> >>>> >>>> -- >>>> _ >>>> / \ >>>> A* \^ - >>>> ,./ _.`\\ / \ >>>> / ,--.S \/ \ >>>> / `"~,_ \ \ >>>> __o ? >>>> _ \<,_ /:\ >>>> --(_)/-(_)----.../ | \ >>>> --------------.......J >>>> Paul Ivanov >>>> http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 >>>> _______________________________________________ >>>> 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 Mon Jul 9 17:18:35 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 9 Jul 2018 17:18:35 -0400 Subject: [Matplotlib-devel] Windows wheels for Python 3.7? In-Reply-To: References: Message-ID: Windows wheels are up (thanks to Christoph Gohlke). Tom On Tue, Jul 3, 2018 at 10:09 AM Matthew Brett wrote: > Hi, > > What is the current procedure for generating Windows wheels? > > As y'all probably know, Python 3.7 came out a few days ago, and we > really need to get a 3.7 wheel out ASAP to help other projects that > depend on Matplotlib. I have done / am doing this for Linux / macOS - > but what should happen next to get wheels for Windows? > > Cheers, > > Matthew > _______________________________________________ > 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 matthew.brett at gmail.com Mon Jul 9 17:36:56 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Mon, 9 Jul 2018 22:36:56 +0100 Subject: [Matplotlib-devel] Windows wheels for Python 3.7? In-Reply-To: References: Message-ID: On Mon, Jul 9, 2018 at 10:18 PM, Thomas Caswell wrote: > Windows wheels are up (thanks to Christoph Gohlke). Excellent - thanks Christoph. Matthew From efiring at hawaii.edu Mon Jul 9 22:00:42 2018 From: efiring at hawaii.edu (Eric Firing) Date: Mon, 9 Jul 2018 16:00:42 -1000 Subject: [Matplotlib-devel] Travis is hosed? Message-ID: <9eeb19cb-485d-f0d5-9adf-a649cad846d3@hawaii.edu> I'm getting a flood of "glyph" warnings, and an odd failure at the bottom of the log. What's going on? Example, from a PR that is passing on Appveyer: https://travis-ci.org/matplotlib/matplotlib/jobs/402005933 Eric From tcaswell at gmail.com Mon Jul 9 22:05:52 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 9 Jul 2018 22:05:52 -0400 Subject: [Matplotlib-devel] Travis is hosed? In-Reply-To: <9eeb19cb-485d-f0d5-9adf-a649cad846d3@hawaii.edu> References: <9eeb19cb-485d-f0d5-9adf-a649cad846d3@hawaii.edu> Message-ID: https://github.com/matplotlib/matplotlib/pull/11614 should hopefully address the tox / pytest related issue (with out compromising test coverage) and https://github.com/matplotlib/matplotlib/pull/11615 reverts the two PRs that are the source of the glyph warnings. Tom On Mon, Jul 9, 2018 at 10:00 PM Eric Firing wrote: > I'm getting a flood of "glyph" warnings, and an odd failure at the > bottom of the log. What's going on? Example, from a PR that is passing > on Appveyer: > > https://travis-ci.org/matplotlib/matplotlib/jobs/402005933 > > Eric > _______________________________________________ > 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 mdboom at gmail.com Thu Jul 12 21:35:27 2018 From: mdboom at gmail.com (Michael Droettboom) Date: Thu, 12 Jul 2018 21:35:27 -0400 Subject: [Matplotlib-devel] Officially passing the baton to Thomas Caswell Message-ID: All, This e-mail is just to announce and make explicit what has already been the case in reality for quite some time (since at least summer of 2016): that the leadership of the matplotlib project is in the very capable hands of Thomas Caswell. His ability to manage such a high velocity of issues and pull requests is beyond astonishing, and he's brought the project forward in ways that seemed remote when my involvement tapered off. Thomas remains a pleasure and inspiration to work with and I know John would be proud of how is creation is being shepherded. As part of formalizing this, there is a pull request to bring the matplotlib governance document draft into effect here: https://github.com/matplotlib/governance/pull/3 Best of luck, and keep up the good work, everyone! Michael Droettboom -------------- next part -------------- An HTML attachment was scrubbed... URL: From anntzer.lee at gmail.com Sun Jul 22 16:52:22 2018 From: anntzer.lee at gmail.com (Antony Lee) Date: Sun, 22 Jul 2018 22:52:22 +0200 Subject: [Matplotlib-devel] mplcairo 0.1 release Message-ID: Dear all, I am pleased to announce the release of mplcairo 0.1 # Description mplcairo is a Matplotlib backend based on the well-known cairo library, supporting output to both raster (including interactively) and vector formats. In other words, it provides the functionality of Matplotlib's {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. Per Matplotlib's standard API, the backend can be selected by calling matplotlib.use("module://mplcairo.qt") or setting your MPLBACKEND environment variable to `module://mplcairo.qt` for Qt5, and similarly for other toolkits. The source tarball, and Py3.6 manylinux and Windows wheels, are available on PyPI (I am looking for help to generate the OSX wheels). See the README for more details. # Why a new backend? Compared to Matplotlib's builtin Agg and cairo backends, mplcairo presents the following features: - Improved accuracy (e.g., with marker positioning, quad meshes, and text kerning). - Support for a wider variety of font formats, such as otf and pfb, for vector (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such fonts). - Optional support for complex text layout (right-to-left languages, etc.) using Raqm. **Note** that Raqm depends on Fribidi, which is licensed under the LGPLv2.1+. - Support for embedding URLs in PDF (but not SVG) output (requires cairo?1.15.4). - Support for multi-page output both for PDF and PS (Matplotlib only supports multi-page PDF). - Support for custom blend modes (see `examples/operators.py`). See the README for more details. # Changelog from mplcairo 0.1a1 to mplcairo 0.1 - Integration with libraqm now occurs via dlopen() rather than being selected at compile-time. - Various rendering and performance improvements. - On Travis, we now run Matplotlib's test suite with mplcairo patching the default Agg renderer. Enjoy, Antony Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Mon Jul 23 13:44:14 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 23 Jul 2018 13:44:14 -0400 Subject: [Matplotlib-devel] mplcairo 0.1 release In-Reply-To: References: Message-ID: Congratulations to Antony for his hard work on this important backend! As far as I am concerned, the cairo backend is the future of matplotlib. Test this backend out for yourselves and help us take matplotlib to the next level in high-quality charting! Cheers! Ben Root On Sun, Jul 22, 2018 at 4:52 PM, Antony Lee wrote: > Dear all, > > I am pleased to announce the release of mplcairo 0.1 > > # Description > > mplcairo is a Matplotlib backend based on the well-known cairo library, > supporting output to both raster (including interactively) and vector > formats. In other words, it provides the functionality of Matplotlib's > {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. > > Per Matplotlib's standard API, the backend can be selected by calling > > matplotlib.use("module://mplcairo.qt") > > or setting your MPLBACKEND environment variable to `module://mplcairo.qt` > for > Qt5, and similarly for other toolkits. > > The source tarball, and Py3.6 manylinux and Windows wheels, are available > on > PyPI (I am looking for help to generate the OSX wheels). > > See the README for more details. > > # Why a new backend? > > Compared to Matplotlib's builtin Agg and cairo backends, mplcairo presents > the > following features: > > - Improved accuracy (e.g., with marker positioning, quad meshes, and text > kerning). > - Support for a wider variety of font formats, such as otf and pfb, for > vector > (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such > fonts). > - Optional support for complex text layout (right-to-left languages, etc.) > using Raqm. **Note** that Raqm depends on Fribidi, which is licensed > under > the LGPLv2.1+. > - Support for embedding URLs in PDF (but not SVG) output (requires > cairo?1.15.4). > - Support for multi-page output both for PDF and PS (Matplotlib only > supports > multi-page PDF). > - Support for custom blend modes (see `examples/operators.py`). > > See the README for more details. > > # Changelog from mplcairo 0.1a1 to mplcairo 0.1 > > - Integration with libraqm now occurs via dlopen() rather than being > selected > at compile-time. > - Various rendering and performance improvements. > - On Travis, we now run Matplotlib's test suite with mplcairo patching the > default Agg renderer. > > Enjoy, > > Antony Lee > > _______________________________________________ > 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 matthew.brett at gmail.com Mon Jul 23 14:52:22 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Mon, 23 Jul 2018 19:52:22 +0100 Subject: [Matplotlib-devel] mplcairo 0.1 release In-Reply-To: References: Message-ID: Hi, Can I help with the macOS wheel build? Cheers, Matthew On Sun, Jul 22, 2018 at 9:52 PM, Antony Lee wrote: > Dear all, > > I am pleased to announce the release of mplcairo 0.1 > > # Description > > mplcairo is a Matplotlib backend based on the well-known cairo library, > supporting output to both raster (including interactively) and vector > formats. In other words, it provides the functionality of Matplotlib's > {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. > > Per Matplotlib's standard API, the backend can be selected by calling > > matplotlib.use("module://mplcairo.qt") > > or setting your MPLBACKEND environment variable to `module://mplcairo.qt` > for > Qt5, and similarly for other toolkits. > > The source tarball, and Py3.6 manylinux and Windows wheels, are available on > PyPI (I am looking for help to generate the OSX wheels). > > See the README for more details. > > # Why a new backend? > > Compared to Matplotlib's builtin Agg and cairo backends, mplcairo presents > the > following features: > > - Improved accuracy (e.g., with marker positioning, quad meshes, and text > kerning). > - Support for a wider variety of font formats, such as otf and pfb, for > vector > (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such > fonts). > - Optional support for complex text layout (right-to-left languages, etc.) > using Raqm. **Note** that Raqm depends on Fribidi, which is licensed > under > the LGPLv2.1+. > - Support for embedding URLs in PDF (but not SVG) output (requires > cairo?1.15.4). > - Support for multi-page output both for PDF and PS (Matplotlib only > supports > multi-page PDF). > - Support for custom blend modes (see `examples/operators.py`). > > See the README for more details. > > # Changelog from mplcairo 0.1a1 to mplcairo 0.1 > > - Integration with libraqm now occurs via dlopen() rather than being > selected > at compile-time. > - Various rendering and performance improvements. > - On Travis, we now run Matplotlib's test suite with mplcairo patching the > default Agg renderer. > > Enjoy, > > Antony Lee > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > From anntzer.lee at gmail.com Mon Jul 23 15:51:51 2018 From: anntzer.lee at gmail.com (Antony Lee) Date: Mon, 23 Jul 2018 21:51:51 +0200 Subject: [Matplotlib-devel] mplcairo 0.1 release In-Reply-To: References: Message-ID: Yes please! The issue is essentially that mplcairo depends on a very recent libc++. For local builds on machines with recent enough tooling (e.g. from homebrew), that's fine, including on OSX ( https://travis-ci.org/anntzer/mplcairo/jobs/406902684 shows that mplcairo does work on Travis); the problem is how to ship the new libc++ with the wheels. On Linux, gcc has -static-libgcc -static-libstdc++ which are basically there exactly for that purpose ( https://github.com/anntzer/mplcairo/blob/master/setup.py#L37), but it's unclear to me how to achieve the same on OSX. Alternatively, if recent-enough OSXes already ship a recent-enough libc++, perhaps we could start with wheels that just target these versions of OSX (not optimal, but better than nothing)? Looking forward to your insights, Antony On Mon, Jul 23, 2018 at 8:52 PM, Matthew Brett wrote: > Hi, > > Can I help with the macOS wheel build? > > Cheers, > > Matthew > > On Sun, Jul 22, 2018 at 9:52 PM, Antony Lee wrote: > > Dear all, > > > > I am pleased to announce the release of mplcairo 0.1 > > > > # Description > > > > mplcairo is a Matplotlib backend based on the well-known cairo library, > > supporting output to both raster (including interactively) and vector > > formats. In other words, it provides the functionality of Matplotlib's > > {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. > > > > Per Matplotlib's standard API, the backend can be selected by calling > > > > matplotlib.use("module://mplcairo.qt") > > > > or setting your MPLBACKEND environment variable to `module://mplcairo.qt` > > for > > Qt5, and similarly for other toolkits. > > > > The source tarball, and Py3.6 manylinux and Windows wheels, are > available on > > PyPI (I am looking for help to generate the OSX wheels). > > > > See the README for more details. > > > > # Why a new backend? > > > > Compared to Matplotlib's builtin Agg and cairo backends, mplcairo > presents > > the > > following features: > > > > - Improved accuracy (e.g., with marker positioning, quad meshes, and text > > kerning). > > - Support for a wider variety of font formats, such as otf and pfb, for > > vector > > (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such > > fonts). > > - Optional support for complex text layout (right-to-left languages, > etc.) > > using Raqm. **Note** that Raqm depends on Fribidi, which is licensed > > under > > the LGPLv2.1+. > > - Support for embedding URLs in PDF (but not SVG) output (requires > > cairo?1.15.4). > > - Support for multi-page output both for PDF and PS (Matplotlib only > > supports > > multi-page PDF). > > - Support for custom blend modes (see `examples/operators.py`). > > > > See the README for more details. > > > > # Changelog from mplcairo 0.1a1 to mplcairo 0.1 > > > > - Integration with libraqm now occurs via dlopen() rather than being > > selected > > at compile-time. > > - Various rendering and performance improvements. > > - On Travis, we now run Matplotlib's test suite with mplcairo patching > the > > default Agg renderer. > > > > Enjoy, > > > > Antony Lee > > > > _______________________________________________ > > 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 matthew.brett at gmail.com Mon Jul 23 15:58:38 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Mon, 23 Jul 2018 20:58:38 +0100 Subject: [Matplotlib-devel] mplcairo 0.1 release In-Reply-To: References: Message-ID: Hi, What version has a late enough libc? It's not problem at at to depend on 10.9, for example. Cheers, Matthew On Mon, Jul 23, 2018 at 8:51 PM, Antony Lee wrote: > Yes please! > The issue is essentially that mplcairo depends on a very recent libc++. For > local builds on machines with recent enough tooling (e.g. from homebrew), > that's fine, including on OSX > (https://travis-ci.org/anntzer/mplcairo/jobs/406902684 shows that mplcairo > does work on Travis); the problem is how to ship the new libc++ with the > wheels. On Linux, gcc has -static-libgcc -static-libstdc++ which are > basically there exactly for that purpose > (https://github.com/anntzer/mplcairo/blob/master/setup.py#L37), but it's > unclear to me how to achieve the same on OSX. Alternatively, if > recent-enough OSXes already ship a recent-enough libc++, perhaps we could > start with wheels that just target these versions of OSX (not optimal, but > better than nothing)? > Looking forward to your insights, > Antony > > On Mon, Jul 23, 2018 at 8:52 PM, Matthew Brett > wrote: >> >> Hi, >> >> Can I help with the macOS wheel build? >> >> Cheers, >> >> Matthew >> >> On Sun, Jul 22, 2018 at 9:52 PM, Antony Lee wrote: >> > Dear all, >> > >> > I am pleased to announce the release of mplcairo 0.1 >> > >> > # Description >> > >> > mplcairo is a Matplotlib backend based on the well-known cairo library, >> > supporting output to both raster (including interactively) and vector >> > formats. In other words, it provides the functionality of Matplotlib's >> > {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. >> > >> > Per Matplotlib's standard API, the backend can be selected by calling >> > >> > matplotlib.use("module://mplcairo.qt") >> > >> > or setting your MPLBACKEND environment variable to >> > `module://mplcairo.qt` >> > for >> > Qt5, and similarly for other toolkits. >> > >> > The source tarball, and Py3.6 manylinux and Windows wheels, are >> > available on >> > PyPI (I am looking for help to generate the OSX wheels). >> > >> > See the README for more details. >> > >> > # Why a new backend? >> > >> > Compared to Matplotlib's builtin Agg and cairo backends, mplcairo >> > presents >> > the >> > following features: >> > >> > - Improved accuracy (e.g., with marker positioning, quad meshes, and >> > text >> > kerning). >> > - Support for a wider variety of font formats, such as otf and pfb, for >> > vector >> > (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such >> > fonts). >> > - Optional support for complex text layout (right-to-left languages, >> > etc.) >> > using Raqm. **Note** that Raqm depends on Fribidi, which is licensed >> > under >> > the LGPLv2.1+. >> > - Support for embedding URLs in PDF (but not SVG) output (requires >> > cairo?1.15.4). >> > - Support for multi-page output both for PDF and PS (Matplotlib only >> > supports >> > multi-page PDF). >> > - Support for custom blend modes (see `examples/operators.py`). >> > >> > See the README for more details. >> > >> > # Changelog from mplcairo 0.1a1 to mplcairo 0.1 >> > >> > - Integration with libraqm now occurs via dlopen() rather than being >> > selected >> > at compile-time. >> > - Various rendering and performance improvements. >> > - On Travis, we now run Matplotlib's test suite with mplcairo patching >> > the >> > default Agg renderer. >> > >> > Enjoy, >> > >> > Antony Lee >> > >> > _______________________________________________ >> > Matplotlib-devel mailing list >> > Matplotlib-devel at python.org >> > https://mail.python.org/mailman/listinfo/matplotlib-devel >> > > > From anntzer.lee at gmail.com Mon Jul 23 16:39:45 2018 From: anntzer.lee at gmail.com (Antony Lee) Date: Mon, 23 Jul 2018 22:39:45 +0200 Subject: [Matplotlib-devel] mplcairo 0.1 release In-Reply-To: References: Message-ID: That's not totally clear to me (I don't actually have an OSX machine available, although I do get ssh access to a not-so-recent one), but by "very recent", I mean something that supports C++17 (e.g. std::variant), so that can't be older than 10.13 (and it's not even certain that that would work). (Perhaps looking into static linking is better indeed :-)) Antony On Mon, Jul 23, 2018 at 9:58 PM, Matthew Brett wrote: > Hi, > > What version has a late enough libc? It's not problem at at to > depend on 10.9, for example. > > Cheers, > > Matthew > > On Mon, Jul 23, 2018 at 8:51 PM, Antony Lee wrote: > > Yes please! > > The issue is essentially that mplcairo depends on a very recent libc++. > For > > local builds on machines with recent enough tooling (e.g. from homebrew), > > that's fine, including on OSX > > (https://travis-ci.org/anntzer/mplcairo/jobs/406902684 shows that > mplcairo > > does work on Travis); the problem is how to ship the new libc++ with the > > wheels. On Linux, gcc has -static-libgcc -static-libstdc++ which are > > basically there exactly for that purpose > > (https://github.com/anntzer/mplcairo/blob/master/setup.py#L37), but it's > > unclear to me how to achieve the same on OSX. Alternatively, if > > recent-enough OSXes already ship a recent-enough libc++, perhaps we could > > start with wheels that just target these versions of OSX (not optimal, > but > > better than nothing)? > > Looking forward to your insights, > > Antony > > > > On Mon, Jul 23, 2018 at 8:52 PM, Matthew Brett > > wrote: > >> > >> Hi, > >> > >> Can I help with the macOS wheel build? > >> > >> Cheers, > >> > >> Matthew > >> > >> On Sun, Jul 22, 2018 at 9:52 PM, Antony Lee > wrote: > >> > Dear all, > >> > > >> > I am pleased to announce the release of mplcairo 0.1 > >> > > >> > # Description > >> > > >> > mplcairo is a Matplotlib backend based on the well-known cairo > library, > >> > supporting output to both raster (including interactively) and vector > >> > formats. In other words, it provides the functionality of > Matplotlib's > >> > {,qt5,gtk3,wx,tk,macos}{agg,cairo}, pdf, ps, and svg backends. > >> > > >> > Per Matplotlib's standard API, the backend can be selected by calling > >> > > >> > matplotlib.use("module://mplcairo.qt") > >> > > >> > or setting your MPLBACKEND environment variable to > >> > `module://mplcairo.qt` > >> > for > >> > Qt5, and similarly for other toolkits. > >> > > >> > The source tarball, and Py3.6 manylinux and Windows wheels, are > >> > available on > >> > PyPI (I am looking for help to generate the OSX wheels). > >> > > >> > See the README for more details. > >> > > >> > # Why a new backend? > >> > > >> > Compared to Matplotlib's builtin Agg and cairo backends, mplcairo > >> > presents > >> > the > >> > following features: > >> > > >> > - Improved accuracy (e.g., with marker positioning, quad meshes, and > >> > text > >> > kerning). > >> > - Support for a wider variety of font formats, such as otf and pfb, > for > >> > vector > >> > (PDF, PS, SVG) backends (Matplotlib's Agg backend also supports such > >> > fonts). > >> > - Optional support for complex text layout (right-to-left languages, > >> > etc.) > >> > using Raqm. **Note** that Raqm depends on Fribidi, which is > licensed > >> > under > >> > the LGPLv2.1+. > >> > - Support for embedding URLs in PDF (but not SVG) output (requires > >> > cairo?1.15.4). > >> > - Support for multi-page output both for PDF and PS (Matplotlib only > >> > supports > >> > multi-page PDF). > >> > - Support for custom blend modes (see `examples/operators.py`). > >> > > >> > See the README for more details. > >> > > >> > # Changelog from mplcairo 0.1a1 to mplcairo 0.1 > >> > > >> > - Integration with libraqm now occurs via dlopen() rather than being > >> > selected > >> > at compile-time. > >> > - Various rendering and performance improvements. > >> > - On Travis, we now run Matplotlib's test suite with mplcairo patching > >> > the > >> > default Agg renderer. > >> > > >> > Enjoy, > >> > > >> > Antony Lee > >> > > >> > _______________________________________________ > >> > 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 Wed Jul 25 19:06:36 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Wed, 25 Jul 2018 19:06:36 -0400 Subject: [Matplotlib-devel] devel list membership Message-ID: Folks, This is cross-posted with (private) github channels. We need a reliable channel to communicate with every one who has a commit bit. Using github likely works (and has the advantage of keeping it's self in sync!), however there does not seem to be a way to have it be public to the world. To that end I propose that if you have commit rights you must also be a member of matplotlib-devel at python.org. Thoughts? Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nathan12343 at gmail.com Wed Jul 25 19:46:28 2018 From: nathan12343 at gmail.com (Nathan Goldbaum) Date: Wed, 25 Jul 2018 18:46:28 -0500 Subject: [Matplotlib-devel] devel list membership In-Reply-To: References: Message-ID: It would be great if matplotlib-devel had more traffic. I often miss interesting discussions because they happen on github and I'm not subscribed to matplotlib's github. On Wed, Jul 25, 2018 at 6:06 PM, Thomas Caswell wrote: > Folks, > > This is cross-posted with (private) github channels. > > We need a reliable channel to communicate with every one who has a commit > bit. Using github likely works (and has the advantage of keeping it's self > in sync!), however there does not seem to be a way to have it be public to > the world. > > To that end I propose that if you have commit rights you must also be a > member of matplotlib-devel at python.org. > > Thoughts? > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > > _______________________________________________ > 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 Wed Jul 25 21:25:38 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Wed, 25 Jul 2018 21:25:38 -0400 Subject: [Matplotlib-devel] Weekly dev meeting Message-ID: Folks, Semi-regular reminder than we have weekly ~hour long dev calls Mondays at 3PM EDT (1900 UTC), all are welcome. The weekly agenda and notes are at https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AIjYEukjsgPCLSQaxQYSioznAg-aAmENlkgepgsMeDZtlsYu We are going to try moving the call from where it is currently hosted to a meeting on NumFOCUS's gsuite. I have invited the current invitation list (filtered by recent attendance) to the new meeting. The link to join the meeting is: https://meet.google.com/rfx-hein-psp I am 50/50 on the new link working as expected / hitch free. If you plan to join, keep an eye on this mailing list / gitter for if we are moving back to the current meeting location for the call. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Thu Jul 26 06:34:18 2018 From: pmhobson at gmail.com (Paul Hobson) Date: Thu, 26 Jul 2018 03:34:18 -0700 Subject: [Matplotlib-devel] devel list membership In-Reply-To: References: Message-ID: I think this makes a lot of sense. Based on my subscriptions to the numpy and scipy lists, there's still plenty of deep-dive developer talk happening on mailing lists. On Wed, Jul 25, 2018 at 4:06 PM Thomas Caswell wrote: > Folks, > > This is cross-posted with (private) github channels. > > We need a reliable channel to communicate with every one who has a commit > bit. Using github likely works (and has the advantage of keeping it's self > in sync!), however there does not seem to be a way to have it be public to > the world. > > To that end I propose that if you have commit rights you must also be a > member of matplotlib-devel at python.org. > > Thoughts? > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > 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: