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

Lukasz Langa lukasz at langa.pl
Sun Nov 5 22:32:30 EST 2017


On 5 Nov, 2017, at 6:29 PM, Oleg Broytman <phd at phdru.name> wrote:

On Sun, Nov 05, 2017 at 09:20:12PM -0500, Yury Selivanov <yselivanov.ml at gmail.com> wrote: Big +1 from me. The whole point of DeprecationWarnings is to be visible The whole point of DeprecationWarnings is to be visible to developers while in reality they will be visible to users -- and what the users would do with the warnings?

Complain to the authors and make them remove the issue.

https://github.com/requests/requests/issues/3954 <https://github.com/requests/requests/issues/3954> https://github.com/scikit-learn-contrib/sklearn-pandas/issues/76 <https://github.com/scikit-learn-contrib/sklearn-pandas/issues/76> https://github.com/pandas-dev/pandas/issues/5824 <https://github.com/pandas-dev/pandas/issues/5824> https://github.com/pypa/setuptools/issues/472 <https://github.com/pypa/setuptools/issues/472>

+1 to re-enable this from me, too. At Facebook we are running unit tests and development builds with warnings. Just be aware that for some applications that will spew a lot. Python 3.6's warnings on invalid escapes is a big source of this.



More information about the Python-Dev mailing list