Change deprecation mechanism to use a function
See original GitHub issueAs discussed in https://github.com/pytest-dev/pytest/pull/7362#issuecomment-649800119_, let’s change our warnings mechanism to include a new PytestExpiredDeprecationWarning
exception which is chosen at runtime depending on the current pytest version.
This will simplify our side because we won’t need to change PytestDeprecationWarning
s into errors anymore before each major release.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
How and When to Deprecate APIs - Oracle Help Center
Java supports two mechanisms for deprecation: and an annotation, (supported starting with J2SE 5.0) and a Javadoc tag (supported since 1.1). Existing calls...
Read more >python - lint usages of functions with @deprecated decorator
I will get a runtime warning when running it as PYTHONWARNINGS="default::DeprecationWarning" python testfile.py but pylint , mypy , and flake8 ...
Read more >How to deprecate classes, methods, arguments and hooks in ...
Add the property $deprecatedPublicMethods to the class and list all methods that should no longer be accessed from outside of the class. Make ......
Read more >Python deprecation - DEV Community
Deprecation on function arguments, requires you to check for your desired changes and throw DeprecationWarning 's withing the method. from ...
Read more >API — Deprecated 1.2.14 documentation - Read the Docs
This adapter is used to get the deprecation message according to the wrapped object type: class, function, standard method, static method, or class...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Remember the stacklevel for warnings.warn:
based on experiences in pip and a few internal tools, the self version dependency seems orders of magnitude better than any manually managed way to deal with it