[issue9501] Logging shutdown regressions with weakrefs

Xavier de Gaye added the comment: Yes, my last two messages refer to python 3.3.0 only. The changes logged in http://bugs.python.org/issue9501#msg180039 do fix the behavior of both versions of teardown_module.py. -- ___ Python tracker

[issue9501] Logging shutdown regressions with weakrefs

Vinay Sajip added the comment: Thanks for hunting these down. With the latest version, neither variant of the teardown script produces any error message on my system, either with 3.3 or 3.4 (default). -- ___ Python tracker

[issue9501] Logging shutdown regressions with weakrefs

Xavier de Gaye added the comment: The initial teardown_module.py can be simply replaced with (not a contrived example anymore) the following statements to print the spurious ignored Exceptions: # Run the script in a loop: # while [ 1 ]; do python3 teardown_module.py; sleep .1; done import loggin

[issue9501] Logging shutdown regressions with weakrefs

Xavier de Gaye added the comment: The reason why this happens in python 3.3.0 and not in 3.2: 1) lastResort holds a reference to an instance of _StderrHandler at module tear down, thus potentially triggering a TypeError in _removeHandlerRef. 2) The logging code has the following two lines

[issue9501] Logging shutdown regressions with weakrefs

Roundup Robot added the comment: New changeset 966887830011 by Vinay Sajip in branch '2.7': Issue #9501: Improved shutdown handling to deal with module attributes correctly. http://hg.python.org/cpython/rev/966887830011 New changeset 8eac88f49cc0 by Vinay Sajip in branch '3.2': Issue #9501: Imp

[issue9501] Logging shutdown regressions with weakrefs

Changes by Xavier de Gaye : -- keywords: +patch Added file: http://bugs.python.org/file28743/teardown_module.diff ___ Python tracker ___ __

[issue9501] Logging shutdown regressions with weakrefs

Xavier de Gaye added the comment: Still randomly getting ignored exceptions on 3.3 and the default branch, got for example: Exception TypeError: TypeError("argument of type 'NoneType' is not iterable",) in ignored This happens in a threaded application. The root cause is explained in http://bug

[issue9501] Logging shutdown regressions with weakrefs

Vinay Sajip added the comment: Fix checked into py3k and release27-maint (r84282). -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue9501] Logging shutdown regressions with weakrefs

Changes by Vinay Sajip : -- assignee: -> vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9501] Logging shutdown regressions with weakrefs

Martin added the comment: For the second case, just reverting the change to Handler.close may be best, I don't see why the module should be keeping responsibility for flushing and closing handlers it no longer has a strong reference to. -- Added file: http://bugs.python.org/file18361/

[issue9501] Logging shutdown regressions with weakrefs

Martin added the comment: This could be fixed in a similar way to was done for the shutdown function in r51206 (which incidentally seems both unnecessary and incomplete - the function runs atexit which precedes module teardown, but also uses the raiseExceptions module global which is not rebo

[issue9501] Logging shutdown regressions with weakrefs

New submission from Martin : With the logging change to using weakrefs for handler cleanup done by the follow-on patch in issue 6615 exceptions may now be thrown during module teardown. There are two distinct problem cases: 1) The new `_removeHandlerRef` function may run during teardown (when