On Fri, Aug 9, 2019 at 12:07 PM <brian.sk...@gmail.com> wrote: > > Eric V. Smith wrote: > > Hopefully the warnings in 3.9 would be more visible that what we saw in > > 3.7, so that library authors can take notice and do something about it > > before 3.10 rolls around. > > Eric > > Apologies for the ~double-post on the thread, but: the SymPy team has figured > out the right pytest incantation to expose these warnings. Given the > extensive adoption of pytest, perhaps it would be good to combine (1) a FR on > pytest to add a convenience flag enabling this mix of options with (2) an > aggressive "marketing push", encouraging library maintainers to add it to > their testing/CI.
Unfortunately, their solution isn't a pytest incantation, it's a separate 'compileall' invocation they run on their source tree. I'm not sure how you'd convert this into a pytest feature, because I don't think pytest always know which parts of your code are your code versus which parts are supporting libraries. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/H36DMKUODHOQOYIIZCKW6LYKSGJLXTT4/
