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
The deprecated check is a great feature, however its tidious if the project checked by mypy is a library which might deprecate functions. These functions are then still exported (e.g. in an init file) and have tests. For all these cases, the deprecated check will find something.
As the mypy config only supports customizations of errors per package but not the customization of packages per rule, this is a missing feature
The text was updated successfully, but these errors were encountered:
Agree it would be useful to have some way to override deprecations. One possible approach: an option to allow a glob and set the deprecation behavior for anything matching that glob. For example, deprecation_override = [["datetime.*", "ignore"], ["asyncio.*", "error"]].
Here is a related suggestion. Allowing * wildcards seems helpful. However, maybe a nested list is a little inconvenient and offers more flexibilty then usually needed. So, maybe sticking to the mentioned suggestion (e.g. deprecated_exclude = ["m1.*", "m2.f"]) would be favourable (for the majority of users)?
Feature
The deprecated check is a great feature, however its tidious if the project checked by mypy is a library which might deprecate functions. These functions are then still exported (e.g. in an init file) and have tests. For all these cases, the deprecated check will find something.
As the mypy config only supports customizations of errors per package but not the customization of packages per rule, this is a missing feature
The text was updated successfully, but these errors were encountered: