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 development?
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?