[Python-ideas] Show deprecation warnings in the interactive interpreter
Terry Reedy
tjreedy at udel.edu
Fri Feb 27 22:12:01 CET 2015
On 2/26/2015 9:43 PM, Nathaniel Smith wrote:
> On Feb 26, 2015 6:20 PM, "Stephen J. Turnbull"
> > Nathaniel Smith writes:
> > > I honestly have no idea what [Terry is] trying to argue.
> >
> > I'm surprised at "no idea". He's been clear throughout that because
> > there are *many* alternative interactive interfaces besides the
> > CPython interpreter itself, to be truly effective the warnings need to
> > be propagated to those, and it's not automatic because most of them
> > don't use the interactive interpreter.
Nice summary, Stephen. Thanks. Add the fact that interactive
development takes place in editable text as well as at a '>>> ' prompt.
In Idle, adding a new statement to the current session at '>>> ' and
hitting return and adding a new statement to a current file and hitting
F5 are similar actions. (And they are handled nearly the same by Idle.)
There are pluses and minuses both ways and I use both, ofter
interleaved. I also noted that I occasionally use the real interactive
interpreter to work on Idle.
Guido said that it is OK to help some but not all, and that he would
leave it to IDE maintainers to extend the idea. Using Nick's hints, I
worked out two ways to apply the idea to Idle, one trivial, one not.
The trivial fix would apply to all code, whether submitted by '\n' or
F5. The other fix could apply to both, probably more easily than not.
> Right, I think everyone can agree with all that.
>
> > since it may annoy
> > more users than would be helped, he doesn't seem to think the change
> > is justified.
>
> ... But afaict Terry has not said one word of this;
Nathanial, you are right here. I like to understand the practical
implications of an idea like this before making a strong judgement.
--
Terry Jan Reedy
More information about the Python-ideas
mailing list