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

Doug Evans
2012-01-12T20:59:16Z

On Thu, Jan 12, 2012 at 10:36 AM, Khoo Yit Phang <khooyp@cs.umd.edu> wrote:
>>> Instead of making a new command, we can add an option to, say "python /i", that forces the interpreter to start, so that you can define a GDB macro that starts a Python interpreter (when from_tty is false). That would retain compatibility with the current behavior.
>>
>> Heh.  / is for display options (e.g. x/i $pc), - is for other kinds of
>> options (e.g. symbol-file -readnow foo).
>> But yeah, that's another alternative.  [It feels more problematic,
>> e.g. the caveat you mention.]
>
> For reference, the caveat I mentioned was in an email rejected by the mailing list server: that was for "python -i" which would disallow the python script "-i".
>
> "python /i" would not have this caveat, since "/i" isn't a valid Python expression.

Yeah, but we shouldn't use /i.
[it also feels a bit too hacky]