On Fri, Nov 10, 2017 at 11:34 PM, Brett Cannon <br...@python.org> wrote: > On Thu, Nov 9, 2017, 17:33 Nathaniel Smith, <n...@pobox.com> wrote: >> - if an envvar CI=true is set, then by default make deprecation warnings >> into errors. (This is an informal standard that lots of CI systems use. >> Error instead of "once" because most people don't look at CI output at all >> unless there's an error.) > > One problem with that is I don't want e.g. mypy to start spewing out > warnings while checking my code. That's why I like Victor's idea of a -X > option that also flips on other test/debug features. Yes, this would also > trigger for test runners, but that's at least a smaller amount of affected > code.
Ah, yeah, you're right -- often CI systems use Python programs for infrastructure, beyond the actual code under test. pip is maybe a more obvious example than mypy -- we probably don't want pip to stop working in CI runs just because it happens to use a deprecated API somewhere :-). So this idea doesn't work. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
