[issue7772] test_py3kwarn fails when running the whole test suite

Florent Xicluna added the comment: Fixed with r82149. -- dependencies: +buildbot: DeprecationWarning not raised for icglue (test_py3kwarn.TestStdlibRemovals) status: open -> closed ___ Python tracker _

[issue7772] test_py3kwarn fails when running the whole test suite

Mark Dickinson added the comment: I very much appreciate flox's efforts here, but IMO we really need some more robust solution to the problem of (testing + global warning state). See also issue 4180. -- ___ Python tracker

[issue7772] test_py3kwarn fails when running the whole test suite

Mark Dickinson added the comment: This still seems to be an issue for OS X. With the current trunk (r79716), I get: Mark-Dickinsons-MacBook-Pro:trunk dickinsm$ ./python.exe -3 ./Lib/test/regrtest.py test_macostools test_py3kwarn test_macostools /Users/dickinsm/python/svn/trunk/Lib/importlib/

[issue7772] test_py3kwarn fails when running the whole test suite

Florent Xicluna added the comment: Fixed with r78815. Issue #7092 should silence py3k warnings (soon). Next step is to activate "-3" on some buildbot. -- assignee: -> flox dependencies: -Test suite emits many DeprecationWarnings when -3 is enabled priority: -> normal resolution: ->

[issue7772] test_py3kwarn fails when running the whole test suite

Changes by Florent Xicluna : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7772] test_py3kwarn fails when running the whole test suite

Florent Xicluna added the comment: Here comes the patch: - use test_support.__warningregistry__ to check past warnings - filter the warnings with "(module|package)", to be sure that they are silenced by "test_support.import_module" - fix test_reduce_move (it failed when run after test_unitte

[issue7772] test_py3kwarn fails when running the whole test suite

New submission from Florent Xicluna : "test_py3kwarn" fails when running the whole test suite This is a known behaviour, because of extension modules loaded by previous tests (which cannot be "reloaded"). However, the warnings module store all the warnings when they appear in a dictionary att