Antony Lee
Antony Lee
I *think* this comes down to the fact that FontProperties should keep track of whether they actually have a user-set fontsize (ditto for other properties) or just get it from...
Closed by #54.
I finally got my hands on a mac to test this with the maces backend, but I still can't reproduce the problem...
Ok, let's close this for now, then.
Closing, as I don't really have anything actionable here :/
I believe this is fixed by https://github.com/matplotlib/matplotlib/pull/24491 (which will be present in the future matplotlib 3.7 release).
See also https://github.com/matplotlib/mplcairo/issues/45#issuecomment-1417967080 and the linked matplotlib-inline pr, which is basically what's missing here, I think. Closing as the resolution is waiting for action on the side of matplotlib-inline.
I am a bit reluctant to turn `first_line` into public API because I think I would actually rather get rid of it even internally and simply replace it by `text.split("\n\n")[0]`,...
OK, I see, this seems reasonable. (Sorry for being difficult, but I try to be conservative with adding new APIs.) One thing I am not so happy with in _parse_docstring...
OK, can you check how HEAD looks to you? Note the API changes noted in the changelog.