Message330831
Would it be more acceptable to use a DeprecationWarning? It's not really the right thing because we're not planning to ever actually remove the functionality. But, we've already gone to a lot of trouble to try to show DeprecationWarnings specifically to devs and not end users (hiding them by default, except if the source was the REPL or a test, getting patches into every test framework to handle this, etc.). And the issues here seem to be identical.
Or maybe LintWarning inherits from DeprecationWarning? Or the share a common superclass? |
|
Date |
User |
Action |
Args |
2018-11-30 22:55:54 | njs | set | recipients:
+ njs, barry, nascheme, rhettinger, terry.reedy, gregory.p.smith, jwilk, steven.daprano, serhiy.storchaka, xiang.zhang, miss-islington |
2018-11-30 22:55:54 | njs | set | messageid: <1543618554.1.0.788709270274.issue34850@psf.upfronthosting.co.za> |
2018-11-30 22:55:54 | njs | link | issue34850 messages |
2018-11-30 22:55:53 | njs | create | |
|