[issue46068] Change use of warnings.warn to logging.warning in a few places

Andrei Kulakov added the comment: https://discuss.python.org/t/logging-warning-vs-warnings-warn/12625/2 -- ___ Python tracker ___

[issue46068] Change use of warnings.warn to logging.warning in a few places

Éric Araujo added the comment: To have a discussion about this, you should open a thread on discuss. -- nosy: +eric.araujo ___ Python tracker ___

[issue46068] Change use of warnings.warn to logging.warning in a few places

Andrei Kulakov added the comment: Raymond: Makes sense; I didn't know there was disagreement about this. I will keep this issue open for a week and then close. -- ___ Python tracker

[issue46068] Change use of warnings.warn to logging.warning in a few places

Raymond Hettinger added the comment: > The downside of making this change is that it may break 3rd party unit tests. I don’t see any upside. The modules in question have been stable for a good while. There’s no benefit to changing them. Also, there is no strong agreement that the standard

[issue46068] Change use of warnings.warn to logging.warning in a few places

Change by Raymond Hettinger : -- Removed message: https://bugs.python.org/msg408512 ___ Python tracker ___ ___ Python-bugs-list

[issue46068] Change use of warnings.warn to logging.warning in a few places

Raymond Hettinger added the comment: > The downside of making this change is that it may break 3rd party unit tests. I don’t see any upside. The modules in question have been stable for a good while. There’s no benefit to changing them. Also, there is no strong agreement that the standard

[issue46068] Change use of warnings.warn to logging.warning in a few places

New submission from Andrei Kulakov : In discussion on https://github.com/python/cpython/pull/29910 related to whether to use warnings.warn or logging.warning, I found two places in the library where it might make sense to change to logging.warning. There's probably other instances where the