Make the "python" command resemble the standard Python interpreter

[Doug Evans]

[sorry, for the resend, didn't realize my mailer would pick rich html]

On Thu, Jan 12, 2012 at 9:51 AM, Doug Evans <dje@google.com> wrote:
> On Thu, Jan 12, 2012 at 9:47 AM,  <Paul_Koning@dell.com> wrote:
>>>...
>>>> - 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.
>>
>> Nice solution.
>
> btw, would we ever want to pass options to the python repl?
> If that might ever occur, then we don't want python with arguments to
> be the old behaviour.

Or preferably have a new command should the need arise (I like
python-repl, but I realize repl may be too obscure :-) ).
[so plain "python" would invoke the repl and "python foo" would
evaluate foo in python]
OK, I think I'm OK with where this is going.