This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Document Backwards Incompatible change to logging in 3.4
Type: behavior Stage: resolved
Components: Documentation Versions: Python 3.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, donspaulding, python-dev, vinay.sajip
Priority: normal Keywords:

Created on 2014-06-13 19:07 by donspaulding, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg220482 - (view) Author: Don Spaulding (donspaulding) Date: 2014-06-13 19:07
Discussion of this issue on ML:

https://mail.python.org/pipermail/python-dev/2014-June/135048.html

The behavior of logging.getLevelName changed in Python 3.4.  Previously when passed a string, it would return the corresponding integer value of the level.  In 3.4 it was changed to match the behavior of its documentation.  The patch can be found in issue #18046.

This seems like something that should be documented somewhere.
msg220535 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2014-06-14 08:27
New changeset 277d099a134b by Vinay Sajip in branch '3.4':
Issue #21752: Documented change to behaviour of logging.getLevelName().
http://hg.python.org/cpython/rev/277d099a134b

New changeset 174c30103b57 by Vinay Sajip in branch 'default':
Closes #21752: Merged update from 3.4.
http://hg.python.org/cpython/rev/174c30103b57
History
Date User Action Args
2022-04-11 14:58:04adminsetgithub: 65951
2014-06-14 08:27:26python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg220535

resolution: fixed
stage: resolved
2014-06-13 22:24:32ned.deilysetnosy: + vinay.sajip
2014-06-13 19:07:49donspauldingcreate