René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"DeprecationWarnings should be visible by default in interactive usage","articleBody":"DeprecationWarning and PendingDeprecationWarning are invisible by default. The rationale for this is that they are only useful to people who are writing code, so they should not be shown to end-users who are merely running code.\n\nIf someone is typing stuff into the interactive REPL or a notebook, though, and the code they type uses some deprecated functionality, then we should actually show them this warning. We know that the author is sitting right there. And they're probably going to take whatever they tested interactively and move it into a more permanent form and ugh.\n\nThis problem is particularly acute for packages that are primarily used through the interactive prompt, like numpy. I'm really tired of getting bugs like this: numpy/numpy#5919\n\nThe solution is simple: when entering interactive mode, IPython should do something like:\n\n```\nwarnings.filterwarnings(\"default\", category=DeprecationWarning, module=\"__main__\")\nwarnings.filterwarnings(\"default\", category=PendingDeprecationWarning, module=\"__main__\")\n```\n\nThis means \"for any `DeprecationWarning` or `PendingDeprecation` warning which is caused by code running in the module with name `\"__main__\"`, use the `\"default\"` handler (which means: display once per line of code that triggered it). (Confusingly, the default handler for these warning messages is not `\"default\"`, but `\"ignore\"`. So overriding the default with `\"default\"` produces a non-default outcome.)\n","author":{"url":"https://github.com/njsmith","@type":"Person","name":"njsmith"},"datePublished":"2015-05-27T08:10:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":23},"url":"https://github.com/8478/ipython/issues/8478"}