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.

Author vinay.sajip
Recipients vinay.sajip, zaneb
Date 2019-09-10.09:03:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> are we here to punish people

No, that's not what I'm saying. But it's not a priority to support situations where people don't follow published APIs and still expect things to work the way they would like. I would prefer people to use setLevel(), as it helps to have consistent usage.

> Certainly the Linux kernel and Windows both have a philosophy of not breaking working userspace code

It's Python's philosophy, too. The philosophy is that of not breaking userspace code *which follows published APIs*. If you use unpublished APIs or rely on implementation details, you're generally on your own. That's the situation here, in reference to code that's out in the wild setting the attribute directly rather than via setLevel().
Date User Action Args
2019-09-10 09:03:27vinay.sajipsetrecipients: + vinay.sajip, zaneb
2019-09-10 09:03:27vinay.sajipsetmessageid: <>
2019-09-10 09:03:27vinay.sajiplinkissue37857 messages
2019-09-10 09:03:26vinay.sajipcreate