The workaround that I use is execfile, i.e.
> IronPythonConsole
>>> execfile('foo.py')
This is exactly what python -i foo.py does for you.
-Jim
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Jacobs
Sent: Tuesday, December 06, 2005 12:41 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Workaround for -i
Edward K. Ream wrote:
>> Shouldn't the -i option actually be stopping IronPython from exiting
>
> Right. That's why opening IronPython from a console is a workaround, not a
> fix.
Technically, a workaround should provide a temporary fix. Simply
stopping the console window from disappearing altogether does not allow
you to inspect interactively, which is the main point of -i.
--
Jonathan
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
