[Python-Dev] Proposal: go back to enabling DeprecationWarning by default (original) (raw)

Philipp A. flying-sheep at web.de
Wed Nov 8 02:47:07 EST 2017

Hi Guido,

As far as I can see, the general consensus seems to be to turn them back on in general: The last person to argue against it was Paul Moore, and he since said:

“OK, I overstated [that you’re ‘hosed’ by DeprecationWarnings appearing]. Apologies. My recollection is of a lot more end user complaints when deprecation warnings were previously switched on than others seem to remember, but I can't find hard facts, so I'll assume I'm misremembering.”

Besides, quite some of the problems people mention would only be fixed by turning them on in general, not with the compromise.

So I don’t think we need a compromise, right?

Best, Philipp

Guido van Rossum <guido at python.org> schrieb am Mi., 8. Nov. 2017 um 03:46 Uhr:

To cut this thread short, I say we should use Nick's proposal to turn these warnings on for main but off elsewhere. (See https://mail.python.org/pipermail/python-dev/2017-November/150364.html.)

-- --Guido van Rossum (python.org/~guido)

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/flying-sheep%40web.de -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171108/2cc99267/attachment.html>

More information about the Python-Dev mailing list