René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[MNT]: consistent formatting arguments","articleBody":"### Summary\n\nI think it would be good to have consistent standards on allowable values for formatting arguments.  As far as I can tell, the argument in #15602, which went in in 3.4, is to not add an f-string version for consistency with the library, but starting in 3.3, f-strings became valid direct input into tick formatters\r\n![image](https://user-images.githubusercontent.com/1300499/185775332-1b01bb56-589a-42b1-83ba-5cf492046527.png)\r\n\r\nThis issue is inspired by #23690 but I didn't want to clobber that discussion with a hashing out of formatting.\n\n### Proposed fix\n\nOne consistent standard for all the free text formatting functionality - ticks, cursers, and artist labeling like bar/contour/etc. The upside is then I think we can move all the fmt argument parsing to one function/module so messy things like distinguishing % from an fstring happen in one place.\n\nMy bias is that most of the formatting arguments should take\n1. format (new and old)\n2. callable, \n3. [most of the tick formatters](https://matplotlib.org/devdocs/api/ticker_api.html?highlight=ticker#tick-formatting) since the tick formatters act on a single tick value at a time and are therefore (mostly? pos seems to always be optional) not really tick specific. \n\n_heavily edited to try and make my proposal clearer_","author":{"url":"https://github.com/story645","@type":"Person","name":"story645"},"datePublished":"2022-08-21T04:53:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/23694/matplotlib/issues/23694"}