> To run Python script from the file, simply run:
> IronPythonConsole whatever.py
Something strange is happening when I do this. If I invoke
IronPythonConsole interactively, I can import winforms. But
something different happens when I execute a file. For example, suppose
ironPythonTest.py c
Option: modify the source code to do a Console.ReadKey() before
exiting. You could also try dumping the output to a file.
-
Keith J. Farmer // [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edward K. Ream
Possible bug 4: Without
There is an easy workaround for the missing -i option: simply invoke the
batch file from an already open console window. That way the console stays
open when the batch file dies.
Edward
Edward K. Ream email: [EMAIL PROTECTE
Hi,
I watched the terrific demo on IronPython with Avalon/WinFX. But I just
can't get it to work. It's probably something very simple which I've missed.
IronPython 0.9.5 on .NET 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
>>> from avalon import *
Unhandled exception:
OK, I think I found the answer out on my own, and it is rather obvious.
I didn't have the WinFX SDK installed, just the run-time.
Thanks,
Robert
___
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython
Hi Edward,
> Edward K. Ream Wrote:
>
> Something strange is happening when I do this. If I invoke
> IronPythonConsole interactively, I can import winforms. But
> something different happens when I execute a file. For
> example, suppose ironPythonTest.py contains:
>
> print 'Hello Iron Pyt
Edward K. Ream wrote:
> There is an easy workaround for the missing -i option: simply invoke the
> batch file from an already open console window. That way the console stays
> open when the batch file dies.
Shouldn't the -i option actually be stopping IronPython from exiting
when it's done run
