-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Show deprecation warnings in doc build? #23866
Copy link
Copy link
Closed as not planned
Labels
API: consistencyDocumentationstatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.Issues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github ActionMarked by the “Stale” Github Action
Description
Metadata
Metadata
Assignees
Labels
API: consistencyDocumentationstatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.Issues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github ActionMarked by the “Stale” Github Action
Problem
#23862 fix a deprecation warning that was triggered by an untested bit of code. However, that code is executed in the documentation build.
Proposed solution
It may make sense to at least let the documentation build show deprecation warnings. It should maybe not error on them, although it somehow would make sense to error on Matplotlib deprecation warnings.