@ainmosni mine are:
No-Gos:
Green flags:
Yellow Flags (that need context):
Totally normal #Python upstream attitude:
1. Ignore a reply on a bug report for 3+ years.
2. Install a #StaleBot in the middle of the night.
3. 7 minutes after the bug is marked stale, claim that you "never heard back on this" and that "the issue was somewhere downstream", without even checking another linked issue.
https://github.com/matplotlib/matplotlib/issues/23384#issuecomment-3652630086
Bug summary Two tests of the matplotlib's test suite are failing with Python 3.11.0b3: FAILED tests/test_backends_interactive.py::test_figure_leak_20490[time_mem1-{'MPLBACKEND': 'qtagg', 'QT_API': ...
@pancake Relative.
The only thing #StaleBot generates are #duplicates due to new tickets being opened with the exact same problem…
I don't deny the issue at hand; I just think that such a massive pile needs to be combed through better by using tags and prioritization. Even if that means one has split the backlog into half a dozen different baskets that read "feedback", "suggestion", "bug", "security", "ui/ux", "building", "l18n/i18n", "accessibility", "reproduceability", etc...