Message304035
I imagine we could make it controlled by the same setting that controls deprecation warnings, with some way to differentiate them if you really need to. I forget exactly how that warning control works, so maybe that would be awkward, but I wouldn't be surprised if it was relatively easy. That way test runners would automatically be enabling the warning without having to do anything. (If a test runner isn't already automatically enabling deprecation warnings, then I doubt it will want to automatically enable future warnings). |
|
Date |
User |
Action |
Args |
2017-10-10 13:09:55 | r.david.murray | set | recipients:
+ r.david.murray, gvanrossum, ncoghlan, serhiy.storchaka, dstufft, hawkowl |
2017-10-10 13:09:55 | r.david.murray | set | messageid: <1507640995.66.0.213398074469.issue31742@psf.upfronthosting.co.za> |
2017-10-10 13:09:55 | r.david.murray | link | issue31742 messages |
2017-10-10 13:09:55 | r.david.murray | create | |
|