Philipp, You seem to have missed Nick's posts where he clearly accepts that a middle ground is necessary. R D Murray is also still unconvinced. (And obviously I myself am against reverting to the behavior from 7 years ago.) If we can't agree on some middle ground, the status quo will be maintained.
On Tue, Nov 7, 2017 at 11:47 PM, Philipp A. <flying-sh...@web.de> wrote: > 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 <gu...@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@python.org >> https://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: https://mail.python.org/mailman/options/python-dev/ >> flying-sheep%40web.de >> > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
