Silent DeprecationWarning suppression in imported modules
Managing deprecation alerts in a large codebase without flooding logs depends on the warnings module’s ordered filter list and each module’s __warningregistry__. The documented default filters ignore DeprecationWarning outside __main__, so third-party deprecations can remain silent unless a filter explicitly opts in. Even after inserting an always action at