[Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff (original) (raw)

Barry Warsaw barry at python.org
Wed Nov 8 21:17:28 EST 2017

On Nov 8, 2017, at 16:10, Nick Coghlan <ncoghlan at gmail.com> wrote:

The rationale for that change was so that end users of applications that merely happened to be written in Python wouldn't see deprecation warnings when Linux distros (or the end user) updated to a new Python version.

Instead they’d see breakage as DeprecationWarnings turned into errors. :(

I’m not saying that Python apps, regardless of who they are provided by, should expose DeprecationWarnings to their end users. I actually think it’s good that they don’t because I don’t think most users care if their apps are written in Python, and wouldn’t know what to do about those warnings anyway. And they do cause anxiety.

I suppose there are lots of ways to do this, but at least I’m pretty sure we all agree that end users shouldn’t see DeprecationWarnings, while developers should.

-Barry

-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <http://mail.python.org/pipermail/python-dev/attachments/20171108/beec45f3/attachment-0001.sig>

More information about the Python-Dev mailing list