You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Doc]: Be more explicit about development dependencies #23831
It is somewhat unclear what explicit dependencies are needed for running certain classes of tests and why certain tests are skipped.
Suggested improvement
Inkscape "to render SVG files" -> "for SVG image tests". Perhaps turning the prose text after the dependency into a column next to the dependency. Another thought is to switch the order and put the reason for the dependency first and then list all of the requirements after that.
To run SVG image tests | Inkscape
To run PDF image tests | ghostscript
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
Do we still want to do this? I see the test (and the other) dependencies are now connected to the relevant requirements, so it looks like this could be closed.
Still want the table but can't figure out a clean way of doing it such that info isn't repeated & there's too much info to get rid of the standalone sections. So I'm gonna close, @greglucas feel free to reopen if info is still missing.
Activity
story645 commentedon Sep 8, 2022
A thing I'd like is maybe moving our dependency sections https://matplotlib.org/devdocs/devel/dependencies.html into a table to make it more clear which are optional for what things.
github-actions commentedon Dec 22, 2025
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
melissawm commentedon Jan 21, 2026
Do we still want to do this? I see the test (and the other) dependencies are now connected to the relevant requirements, so it looks like this could be closed.
timhoffm commentedon Jan 21, 2026
The current state is good enough for me. Fine with closing.
story645 commentedon Jan 21, 2026
Still want the table but can't figure out a clean way of doing it such that info isn't repeated & there's too much info to get rid of the standalone sections. So I'm gonna close, @greglucas feel free to reopen if info is still missing.