René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[MNT]: Is broken_barh redundant?","articleBody":"### Summary\n\n`broken_barh()` [documentation ](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.broken_barh.html )does not mention [`barh()`](https://matplotlib.org/stable/api/_as_gen/matplotlib.pyplot.barh.html) but they seem very similar. I'm able to replace calls to `broken_barh()` with a call to this:\r\n```python\r\ndef broken_barh_using_barh(ax, xranges, yrange, **kwargs):\r\n    kwargs2={'align':'edge'} \r\n    for k,v in kwargs.items():\r\n        if k == 'facecolors':\r\n            kwargs2['color'] = v\r\n        else:\r\n            kwargs2[k] = v\r\n    ax.barh(y=yrange[0], height=yrange[1], left=[x[0] for x in xranges], width=[x[1] for x in xranges], **kwargs2)\r\n```\r\n\r\nSo is there something that `broken_barh()` offers that `barh()` doesn't?\r\n\n\n### Proposed fix\n\nIt would help to document the difference if there is a meaningful one, otherwise perhaps deprecate `broken_barh()`.","author":{"url":"https://github.com/omasoud","@type":"Person","name":"omasoud"},"datePublished":"2022-12-27T23:52:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/24827/matplotlib/issues/24827"}