I think the resistance to trace is that it splits an existing level into two,
supporting "level inflation."
The current level name of critical is similar, describing not just an error, but
a really big error!
Note (as described here), handles an additional use case. I don't consider it
level inflation.
-Mike
On 2017-11-28 12:17, Serhiy Storchaka wrote:
28.11.17 21:45, Guido van Rossum пише:
These look like good improvements. I think you should make an issue on
bugs.python.org <http://bugs.python.org> describing your proposal and if you
can submit a PR that implements it.
See https://bugs.python.org/issue31732
It was discussed and rejected. Citing Raymond: "Overall, this seems rehash and
second guess the discussions and decisions made 15 years ago when PEP 282 was
accepted."
The set of logging levels is not closed. The user can extend it to cover more
specialized uses by logging.addLevelName(). There are disadvantages of having
too much standard names for logging levels (as we can see in Java).
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
