René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Better document Axes.set()","articleBody":"### Problem\r\n\r\nThe property batch setter is a nice way for a more compact configuration compared to various lines of `ax.set_*()` calls.\r\n\r\n(Note: using kwargs is quite common with other plotting libraries, so this approach seems generally appealing).\r\n\r\n`Axes.set()` is essentially undocumented:\r\n\r\n- It doesn't show up in the API docs anymore https://matplotlib.org/devdocs/api/axes_api.html. It used to here https://matplotlib.org/3.2.2/api/axes_api.html#bulk-property-manipulation, but was removed as part of #14960.\r\n- Currently there is only https://matplotlib.org/devdocs/api/_as_gen/matplotlib.artist.Artist.set.html\r\n  and that content is far too general and too abstract to be of any help.\r\n\r\n### Suggested Improvement\r\n\r\n- We should re-introduce `Axes.set` into the API docs.\r\n- That method needs a more approachable description than \"A property batch setter. Pass kwargs to set properties.\"\r\n- Ideally, the signature should be explicit and not `**kwargs`, which would enable completion. There are two possible ways of doing this:\r\n\r\n  1. Dynamically rewrite the signature.\r\n  2. Hard-code the signature and add a test, that the parameters match the available properties.\r\n\r\n  The first one has the advantage that this would trivially expand to all artists.\r\n  The second one has the advantage that we can easily specify a meaningful order. Since we rarely change the available properties, hard-coding with a test would be good enough.\r\n","author":{"url":"https://github.com/timhoffm","@type":"Person","name":"timhoffm"},"datePublished":"2021-04-06T20:11:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/19884/matplotlib/issues/19884"}