[issue36704] logging.FileHandler currently hardcodes errors='strict'

Vinay Sajip added the comment: Fixed as part of the fix for bpo-37111. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.9 -Python 3.7 ___ Python tracker ___

[issue36704] logging.FileHandler currently hardcodes errors='strict'

Alan Jenkins added the comment: Oops. I assumed logging.raiseExceptions == True (the default) actually raises exceptions, but it doesn't. It prints the exception to stderr and continues. E.g. traditional UNIX daemons run with stderr connected to /dev/null. Consider during development / deb

[issue36704] logging.FileHandler currently hardcodes errors='strict'

Alan Jenkins added the comment: > [**] dnf developers did not appear to work on the correctness issue they > found. It might be a bug in gettext. Nitpick: sorry, I read too quickly. dnf *did* fix the specific correctness issue, as well as setting raiseExceptions = false. It is explained b

[issue36704] logging.FileHandler currently hardcodes errors='strict'

Change by SilentGhost : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue36704] logging.FileHandler currently hardcodes errors='strict'

New submission from Alan Jenkins : ## Problem description ``` import os import logging logging.basicConfig(filename='example.log',level=logging.DEBUG) for name in os.listdir(): logging.error('Hypothetical syntax error at line 1 of file: {}'.format(name)) ``` The above program is incorrec