[python-committers] Deprecation Policy PEP
tjreedy at udel.edu
Sat Jan 30 04:24:44 EST 2016
On 1/30/2016 3:39 AM, Nick Coghlan wrote:
>> Me too, but only if you add a PendingDeprecationWarning to
>> PendingDeprecationWarning <wink>.
> There were some discussions a while back of restoring a distinction
> between the two by having code executed directly at the REPL (whether
> at the command line or in IDLE) show DeprecationWarning by default,
> but still hide PendingDeprecationWarning globally.
What would you do for mixed start-batch, switch to interactive mode
(-i)? Turn DWs on at the beginning on the basis that -i is mainly for
> That idea actually seemed to garner general approval, so I suspect the
> main reason the discussion died out was the fact that it's a bit
> fiddly to implement.
IDLE executes usercode with, I believe, exec(code_object, pseudo_main).
Does exec simply use the current warnings setting?
More information about the python-committers