New submission from Andrei Kulakov <andrei....@gmail.com>:
In #41322 the behavior of returning a value!=None from test methods was deprecated, there are currently a few tests in Python that do that; it would be good to fix them to be consistent with our deprecation requirement and to avoid deprecation warnings in test runs; it may also possibly surface unexpected issues when reviewing these tests. - there are two distutils tests - test_quiet and test_no_optimize_flag -- probably not worth it to investigate them as distutils is set for removal in 3.12 - test_null_strings in CAPI - test_constructor in test_code I'll try to fix the two tests above today. ---------- components: Tests messages: 400083 nosy: andrei.avk priority: normal severity: normal status: open title: Clean up a few tests that return a value!=None _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44980> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
