Message304033
So you're proposing a coordinated effort across the half dozen, possibly more, test runners to enable some flags, so CPython doesn't log a single message, possibly two, that you're using unsupported experimental software with no backwards compatibility guarantee?
I think the warnings control setting there could be a good solution for your "I don't care, don't show the warning" use case, but I also think explicit disabling per module is a better solution to recommend to users (since we might know that we're using typing, and we say "we are okay with using typing", but might not realise that we're silencing a new provisional module used by an updated library sometime in the future). |
|
Date |
User |
Action |
Args |
2017-10-10 13:05:35 | hawkowl | set | recipients:
+ hawkowl, gvanrossum, ncoghlan, r.david.murray, serhiy.storchaka, dstufft |
2017-10-10 13:05:35 | hawkowl | set | messageid: <1507640735.38.0.213398074469.issue31742@psf.upfronthosting.co.za> |
2017-10-10 13:05:35 | hawkowl | link | issue31742 messages |
2017-10-10 13:05:35 | hawkowl | create | |
|