Re: Make the "python" command resemble the standard Python interpreter

[Doug Evans <dje@google.com>]

On Thu, Jan 12, 2012 at 9:38 AM, Doug Evans <dje@google.com> wrote:
> On Thu, Jan 12, 2012 at 9:30 AM,  <Paul_Koning@dell.com> wrote:
>> Yes, but I think the benefits outweigh the small imcompatibility.
>
> Yes and no.
> - I may want a script that invokes python interactively.
> - How do I write a gdb macro that invokes the python repl?
>
> Solve those problems, and provide a migration path away from the old
> behaviour, and then you've got something.

As a strawman, a new command, python-foo, could be provided
[python-code?  python-script?] that had the "old" behaviour.

As for migration, we *could* add python-foo as an alias for python to
7.4 (seems safe enough) and say the "python" command will change it's
behaviour in 7.5 (or some such).
Or we could just skip the first step and just say python will change
incompatibly in 7.5.
[I don't have a preference, but I think we need to start doing this
kind of thing, and this would be good practice. :-)]