[issue46332] Use raise..from in logging/config instead of assigning __cause__

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46332] Use raise..from in logging/config instead of assigning __cause__

Irit Katriel added the comment: New changeset 0d639678d33a0f085851a07259b8fe2782943118 by Irit Katriel in branch 'main': bpo-46332: use raise..from instead of assigning __cause__ and raising (GH-30517) https://github.com/python/cpython/commit/0d639678d33a0f085851a07259b8fe2782943118 ---

[issue46332] Use raise..from in logging/config instead of assigning __cause__

Change by Irit Katriel : -- Removed message: https://bugs.python.org/msg410218 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue46332] Use raise..from in logging/config instead of assigning __cause__

Irit Katriel added the comment: Lib/logging/config.py has this, which looks like it's partly remnants of old exception handling APIs: except ImportError: e, tb = sys.exc_info()[1:] v = ValueError('Cannot resolve %r: %s' % (s, e)) v.__cause__, v.__traceback__ = e, tb raise v

[issue46332] Use raise..from in logging/config instead of assigning __cause__

Change by Irit Katriel : -- keywords: +patch pull_requests: +28719 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30517 ___ Python tracker ___ ___

[issue46332] Use raise..from in logging/config instead of assigning __cause__

Change by Irit Katriel : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue46332] Use raise..from in logging/config instead of assigning __cause__

New submission from Irit Katriel : Lib/logging/config.py has this, which looks like it's partly remnants of old exception handling APIs: except ImportError: e, tb = sys.exc_info()[1:] v.__cause__, v.__traceback__ = e, tb raise v It is clearer if written as: except ImportError as