[issue27935] logging level FATAL missing in _nameToLevel

2016-09-03 Thread Ondřej Medek
Ondřej Medek added the comment: Just a comment to the https://hg.python.org/cpython/rev/85f9f8bf2ec8 It's functionality is right. It's just a little bit weird, that two derived levels in _nameToLevel: 'FATAL' maps to FATAL, i.e. itself, while 'WARN' maps to the WARNING, i.e. to the main level

[issue27935] logging level FATAL missing in _nameToLevel

2016-09-03 Thread Roundup Robot
Roundup Robot added the comment: New changeset 85f9f8bf2ec8 by Vinay Sajip in branch 'default': Closes #27935: returned numeric value for 'FATAL' logging level. https://hg.python.org/cpython/rev/85f9f8bf2ec8 -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> c

[issue27935] logging level FATAL missing in _nameToLevel

2016-09-03 Thread Vinay Sajip
Vinay Sajip added the comment: As this is an (admittedly small) change in behaviour, I'll apply in 3.6. -- versions: +Python 3.6 -Python 3.5 ___ Python tracker ___ __

[issue27935] logging level FATAL missing in _nameToLevel

2016-09-02 Thread Xiang Zhang
Xiang Zhang added the comment: Though FATAL is not mentioned in the doc, but I think it should be added to getLevelName, just like how WARN is handled now: >>> logging.getLevelName("WARN") 30 -- keywords: +patch nosy: +xiang.zhang Added file: http://bugs.python.org/file44343/issue27935

[issue27935] logging level FATAL missing in _nameToLevel

2016-09-02 Thread SilentGhost
Changes by SilentGhost : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue27935] logging level FATAL missing in _nameToLevel

2016-09-01 Thread Ondřej Medek
New submission from Ondřej Medek: logging.__init__._nameToLevel is missing 'FATAL' key: >>> logging.getLevelName('FATAL') 'Level FATAL' Expected same as: >>> logging.getLevelName('CRITICAL') 50 -- components: Library (Lib) messages: 274204 nosy: Ondřej Medek priority: normal severity: