Mailman 3 February 2017 - Matplotlib-devel

Confusion about draw_artist
by Matthew Brett April 1, 2017

April 1, 2017

Hi, We're using 'draw_artist' in an image viewer, and I just found that our viewer is crashing using the macosx backend. Here's a minimal example: import matplotlib matplotlib.use('macosx') import matplotlib.pyplot as plt fig, ax = plt.subplots(1, 1) im = plt.imshow([[1, 2], [3, 4]]) fig.canvas.draw() ax.draw_artist(im) This generates: Traceback (most recent call last): File "draw_artist.py", line 8, in <module> ax.draw_artist(im) File "/Users/mb312/dev_trees/matplotlib/lib/matplotlib/axes/_base.py", line 2423, in draw_artist raise AttributeError(msg) AttributeError: draw_artist can only be used after an initial draw which caches the render for the macosx backend, and works correctly for the tkagg backend. I can't see any way to cache the renderer here - could someone give me a pointer? Cheers, Matthew

2 5

clearing 'request changes' review
by Thomas Caswell March 24, 2017

March 24, 2017

Folks, I propose the following: - if you would be happy with any other dev clearing the review leave a note saying so explicitly - the default (no note) is to not dismiss other devs reviews, but if there is otherwise consensus and the 'request changes' reviewer is non-responsive, it may be cleared (use your judgement folks!) - if you want to block merging until you re-review it, leave a note saying so. Tom

3 2

[PATCH] Use XDG config path on FreeBSD
by aufc＠cock.li Feb. 21, 2017

Feb. 21, 2017

Hello Matplotlib-Devel, I would like to submit a patch that enables the use of XDG config directory on FreeBSD, which makes sense for regular users. The patch is trivial. Cheers, Adam

2 4

reducing the size of the docs repo
by Thomas Caswell Feb. 21, 2017

Feb. 21, 2017

Folks, We deploy the webpage via https://github.com/matplotlib/matplotlib.github.com however the repository is currently ~6.5GB. I propose we shrink this by: - delete all of the beta/rc docs builds from 2.0 - delete all but the last version of A.B.x docs (and symlink the other versions to the last one - squash the whole repo to a single commit and force-push Going forward, pushing new docs would do the same thing (link + squash + force-push). Tom

1 0

Announcing: Docathon, week of 6 March 2017
by Nelle Varoquaux Feb. 16, 2017

Feb. 16, 2017

Hi everyone, As some of you already know, some of us are involved in the organization of a docathon. Several of us will be meeting up to sprint on documentation or documentation-related projects at Berkeley, New York and Seattle. If you are interested in joining us, either remotely or on campus, don't hesitate to join! Cheers, Nelle *What's a Docathon?* It's a week-long sprint where we focus our efforts on improving the state of documentation in the open-source and open-science world. This means writing better documentation, building tools, and sharing skills. *Who’s this for?* Anyone who is interested in improving the understandability, accessibility, and clarity of software! This might mean developers with a particular project, or individuals who would like to contribute to a project. You don’t need to use a specific language (though there will be many Python and R developers) and you don’t need to be a core developer in order to help out. *Where can I sign up?* Check out the *Docathon website* <https://bids.github.io/docathon/>. You can sign up as a *participant* <https://goo.gl/forms/AaW2b24mMxOutxt02>, *suggest a project* <https://goo.gl/forms/0cPpw01zehrEyDDE3> to work on, or sign up *to host your own* <https://bids.github.io/docathon/pages/hosting.html> remote Docathon wherever you like. You don’t have to use a specific language - we’ll be as accommodating as possible! *When is the Docathon?* The Docathon will be held *March 6 through March 10*. For those coming to BIDS at UC Berkeley, on the first day we'll have tutorials about documentation and demos of documentation tools, followed by a few hours of hacking. During the middle of the week, we'll set aside a few hours each afternoon for hacking as a group at BIDS. On the last day, we'll have a wrap-up event to show off what everybody worked on. *Where will the Docathon take place?* There are a *few docathons being held simultaneously* <https://bids.github.io/docathon/pages/hosts.html>, each with their own schedule. At Berkeley we'll have a physical presence at BIDS over the week, and we encourage you to show up for the hours we set aside for doc hacking. However, it is totally fine to work remotely; we will coordinate people via email/GitHub, too. *Where can I get more information?* Check out an updated schedule, list of tutorials, and more information at our website here: *bids.github.io/docathon* <http://bids.github.io/docathon> . *Contact* If you have any questions, open an issue on our *GitHub repo* <https://github.com/BIDS/docathon>. We look forward to hearing from you! Please feel free to forward this email to anyone who may be interested. We'd love for other institutions/groups to get involved.

1 0

moving examples
by Thomas Caswell Feb. 15, 2017

Feb. 15, 2017

Folks, The examples have been getting a lot of attention recently (much credit to Nelle who is leading that effort) which is great! However I am a bit worried about moving/renaming examples as it will break peoples bookmarks. How much do we care about that (I may be being overly worried/cautious here)? What are our options for leaving bread-crumbs / forwards for people? Tom

6 7

2017-02-13 phone call notes
by Thomas Caswell Feb. 13, 2017

Feb. 13, 2017

Folks, Continuing to experiment with exactly how to do these notes Ryan May, Eric Firing, Thomas Caswell, Nelle Varoquaux ** [[mpl:8032]] - Nelle suggests we replace dots with _actually_ dotted (round dots) - Eric points out it was never super dotted Conclusions: - get rid of clipping - make the 'dotted' pattern square - adjust the rest of the patterns to scale for dropping clipping - make sure all default patterns are commensurate (2 '--' to 4 ':' to 1 '-.') Other comments - merge the loosening of the `grid.linestyle` rcparam to accept dash patterns for 2.0.1 - merge the 'loose' version of patterns for 2.1 - can get 'true dotted' with =dash_capstyle = 'round'= + =[.000001, 1.5]= as the dash pattern ** code for playing with dash patterns #+BEGIN_SRC python import matplotlib.pyplot as plt from cycler import cycler plt.ion() fig, ax = plt.subplots() patterns = cycler('dashes', [(1, 1), (1.1, 1.1), (1, 2), (1, 3)]) * cycler('lw', [1, 1.5, 2, 3, 7, 10]) plt.rcParams['lines.dash_capstyle'] = 'butt' for j, m in enumerate(patterns): ax.plot([0, 1], [100 - j, 100 - j], **m, label=(str(m))) ax.legend() #+END_SRC #+BEGIN_SRC python import matplotlib.pyplot as plt from cycler import cycler plt.ion() fig, ax = plt.subplots() patterns = cycler('lw', [1, 1.5, 2, 3, 7, 10]) * cycler('linestyle', ['--', ':', '-.']) plt.rcParams['lines.dash_capstyle'] = 'butt' for j, m in enumerate(patterns): ax.plot([0, 1], [100 - j, 100 - j], **m, label=(str(m))) ax.legend() #+END_SRC

1 0

Docathon: let's get excited about writing documentation!
by Nelle Varoquaux Feb. 9, 2017

Feb. 9, 2017

Hi Matplotlib team! As we've been hinting both on the gitter chanel and in the emails, some of us are involved in organizing a docathon. The goal is to try to have opensource developers focus on writing and improving documentation for one week! Some cities will be able to have a dedicated place for developers to meet, but most of it should happen remotely. I will be participating with the goal to improve Matplotlib's documentation. Both Thomas and Hannah will also participate. I was wondering if other people would be interested in participating: it can be first by just reviewing documentation related pull request this week or by actually working on improving our documentation. If other people are interested, we can set a list of goals both for us to focus on but also for new contributors to help us. Here are a couple of ideas. - integrate Nicolas Rougier's matplotlib tutorial to our documentation. I believe we have his permission to do this, but this might be worth checking. - re-organize a bit the website to have the tutorials more prominent. - finish the sphinx-gallery migration. If we all did 10 examples, it could easily be done during that week. - Set up sklearn's really cool tool to help review documentation related pull request. (I actually hope to have this done *before* the docathon). - (not doable in a week but overall better website organization) Any ideas and contributions welcome Cheers, N

1 0

2017-02-06 phone call notes
by Thomas Caswell Feb. 7, 2017

Feb. 7, 2017

Folks, It was only my self and Ryan May (dopplershift). We primarily talked through reviewing PRs. Decided to adjust the algorithm for scaling the dash-patterns, see https://github.com/matplotlib/matplotlib/pull/8032 for the result of that discussion. This is a minor API break from 2.0, but I think it is fair to use 2.0.1 to clean up some rough edges (and bend sem-ver a bit). I have been going back and forth on using github handles vs names in listing who is on the call. I think I am going to settle on gh handle + the name you expose on your github profile. Please let me know if this is not acceptable to anyone. Tom

1 0