Mailman 3 July 2019 - Matplotlib-devel

What is draw_path's transform's destination?
by Rob McDonald Sept. 24, 2019

Sept. 24, 2019

I'm implementing a custom path effect by inheriting from AbstractPathEffect and implementing draw_path as instructed here <https://matplotlib.org/api/patheffects_api.html#matplotlib.patheffects.Abst…>. That link references RenderBase.draw_path <https://matplotlib.org/api/backend_bases_api.html#matplotlib.backend_bases.…> to define the required interface. Unfortunately, I can't find anywhere in the associated documentation that tells me what the transform argument really entails. I've also read the transforms tutorial <https://matplotlib.org/tutorials/advanced/transforms_tutorial.html>, and while that explains the pipeline and all the intermediate transformations, it doesn't really settle what I have available to me in draw_path. It is clear that I can use it to transform coordinates from data to something -- but I don't know what to. For the big picture -- I am implementing a path effect to allow drawing hatched lines similar to this <https://www.mathworks.com/matlabcentral/fileexchange/29121-hatched-lines-an…>, which I did years ago in Matlab. Years before that, I've also done this in Java Graphics2D by implementing a custom stroke. (The Java approach is more applicable to the path effect approach, but I can't point to that code online anywhere.) Anyway, I have things mostly working -- and I am using the transform to go from data coordinates to something that looks orthogonal and reasonable on-screen. So, for minimum functionality, it works. However, I want to give the user the ability to control the length and spacing of the hatches -- which is in a coordinate system after the transformation is applied. So, in order to document this thing, I need to know what it is. Or, if there is a way to get intermediate stages of the transformation pipeline, that would work too. As for the user interface -- it seems to make the most sense to specify the hatch length and spacing in terms of something similar to a line width (typically points) or a marker size. I'm new to Python and matplotlib -- what is the Pythonic unit a user would expect to specify this in (and how do I achieve that with what is available in draw_path)? Thanks, Rob

2 5

triage rights for all contributors
by Thomas Caswell July 16, 2019

July 16, 2019

Folks, Discussed on todays call, github has added some additional access levels to orgs (see https://help.github.com/en/articles/repository-permission-levels-for-an-org… and we are proposing giving triage rights to people when they have their first PR merged. I have created a new team "Contributors" and given it triage power of Matplotlib (https://github.com/orgs/matplotlib/teams/contributors). If there are no protests, I will write a script to invite anyone who has a merged PR in the last 12 months and add them to that team. Tom -- Thomas Caswell tcaswell(a)gmail.com

2 1

Using towncrier to generate changelogs
by David Stansby July 15, 2019

July 15, 2019

Dear all, I am proposing to change up how Matplotlib's API changes/what's new pages are generated, in particular moving to using towncrier <https://github.com/hawkowl/towncrier> to add more automation to the process. This is motivated by the crazy amount of time it took me to combine all the API change and what's new fragments into a coherent page for the 3.1.0 release. The PR to change this process is here: https://github.com/matplotlib/matplotlib/pull/14589 The new process would be - When a new feature or api change or code removal is implemented, add a changelog file to the *changelog/* folder - The changelog file should be named <PR number>.<type>.rst, and should contain a single sentence or paragraph describing the change. <type> is the type of change, ie. api_change, new_feature or removal - towncrier can then automatically collate these fragments into a single .rst page, which can be manually edited if needed before releasing I think this will significnatly reduce the burden of producing what's new pages each release, without adding any extra burden on those writing the what's new entries. Please take a look at the PR and leave comments/questions/suggestions! In particular, feedback on what "types" of changelog entry to include would be very welcome. All the best, David

2 2

Table and blume
by swfiua＠gmail.com July 8, 2019

July 8, 2019

Hi, I just wanted to give an update on where I am with the table code. I've been away from the code much of the last month. I've started a project https://github.com/swfiua/blume which has my preferred version of the table code. It's got basic instructions on how to use and then a bunch of questions of where to go from here. The docs folder has some history. I'm at the point now where I think you have better behaviour for most of the known issues, but with some potential impact on users. Those that just use the table function and don't probe into the insides will likely only notice more legible tables. It would be good to think about the end goal here, as that has some bearing on how blume should proceed. I've not got too much further forward beyond a bunch of thinking on what belongs where and how to get there. And also I've been spending some time in my karma pi project looking for other pieces that are in the wrong place. Primarily, it would be good to give everyone access to a better table, just a question of how to get there and are there any precedents for splitting stuff into side projects? Once we have a plan I'll tidy up the issues on github accordingly and work to move the plan along. Johnny

1 0

REL: Matplotlib 3.1.1
by Paul Ivanov July 3, 2019

July 3, 2019

Hi everyone, We are happy to announce the release of Matplotlib 3.1.1! Matplotlib 3.1.1 supports Python 3.6+. This is mostly a bug-fix release, with one API change involving Locator.nonsingular return order. Locator.nonsingular (introduced in matplotlib 3.1.0) now returns a range v0, v1 with v0 <= v1. This behavior is consistent with the implementation of nonsingular by the LogLocator and LogitLocator subclasses. Thanks to everyone who contributed to this release, including 29 folks and one robot who worked together to get 120 pull requests in [1], as well as all the amazing users who reported and raised the issues in the first place. Also a personal thank you to the matplotlib developers who were patient with me making my first solo release. I promise I'll be faster the next go around. :) best, pi 1. https://matplotlib.org/users/github_stats.html -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S \/ \ / `"~,_ \ \ __o ? _ \<,_ /:\ --(_)/-(_)----.../ | \ --------------.......J Paul Ivanov https://pirsquared.org <http://pirsquared.org> | GPG/PGP key id: 0x0F3E28F7

1 0