[issue14784] Re-importing _warnings changes warnings.filters

2016-04-12 Thread Martin Panter
Changes by Martin Panter : -- resolution: -> duplicate status: open -> closed superseder: -> test_warnings modifies warnings.filters when running with "-W default" ___ Python tracker

[issue14784] Re-importing _warnings changes warnings.filters

2014-12-10 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Issue18383 is a duplicate of this issue but it has a patch (not perfect). -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14784

[issue14784] Re-importing _warnings changes warnings.filters

2014-07-04 Thread Mark Lawrence
Mark Lawrence added the comment: I've just tried this and didn't see anything about warnings.filters changed. Full test run output in attached file. -- nosy: +BreamoreBoy Added file: http://bugs.python.org/file35848/Issue14784.log ___ Python

[issue14784] Re-importing _warnings changes warnings.filters

2012-05-12 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14784 ___

[issue14784] Re-importing _warnings changes warnings.filters

2012-05-11 Thread Brett Cannon
New submission from Brett Cannon br...@python.org: If you run test.test_warnings it reports that warnings.filters changed. If you comment out the import of c_warnings in that module, the warning goes away (this happens with running on tests). It looks like _PyWarnings_Init() itself doesn't