Thank you very much, Martin. The problem has been fixed. I also find that
IP 1.0 Beta fixed
this bug. It really sounds great.
Happy new year and cheer for IP!
-Original Message-
The failure is related to the STAThread attribute on IronPythonConsole's
Main. We removed it recently to fi
Hi there!
I'm having trouble with the Avalon
tutorial.
In fact, I can't even start... this is the reeor
message I get when trying to initialize Windows Presentation
Foundation:
>>> from avalon import *Traceback
(most recent call last): File , line 0, in input##0 File
C:\Documents and
I am in a similar situation but not only with avalon.
When I try to invoke "from System.Windows.Forms
import *" I receive the folowing error
Traceback (most recent call last):
File , line 0, in input##26
ImportError: cannot import Windows from System
With System.Drawing too.
With Avalon
Are you using ip.bat or ironpythonconsole.exe?
___
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Hi,
If the question is for mi I use both (ip.bat,
IronPythonConsole.exe) and I receive the same result.
- Original Message -
From:
jeff
sacksteder
To: Discussion of IronPython
Sent: Monday, January 02, 2006 5:53
PM
Subject: Re: [IronPython] Avalon
tutorial
> Are you
using ip.bat or ironpythonconsole.exe?
I'm using both with the same result.
By the way, I'm also having trouble with the
winforms tutorial, just like Catalin:
>>> from System.Windows.Forms import
*Traceback (most recent call last): File , line 0, in
input##0ImportError: cannot
As for the winforms
tutorial, I suspect you are forgetting to do “import winforms”.
However, the winforms.py refers to an old namespace IronPython.Objects that was
renamed to IronPython.Runtime After making the change, all works fine.
The Avalon works just
fine, as far as I can tell. Ho
> As for the winforms tutorial, I suspect you are forgetting to do "import
> winforms"
Well, actually this is what happens when trying to import winforms:
>>> import winforms
Traceback (most recent call last):
File , line 0, in input##0
File C:\Documents and
Settings\Usuario1\Escritorio\Iro
Unfortunately, this is something we broke in Beta 1. The somewhat good news is
the bug is limited to interactive console.
Thanks for letting us know the fix will come soon.
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Sunda
Yep, as I said before, we renamed the namespace IronPython.Objects to
IronPython.Runtime and I didn't update the winforms.py file. Changing the
import statement in the winforms.py to be:
from IronPython.Runtime import CallTarget0
will get you going on the winforms front. Not sure what the Avalo
> Changing the import statement in the winforms.py to be:
> from IronPython.Runtime import CallTarget0 will get you going on the
> winforms front.
Still not working...
>>> from IronPython.Runtime import CallTarget0
>>> from System.Windows.Forms import *
Traceback (most recent call last):
File
I may not have given clear answer last time. Here is the whole thing:
My winforms.py with the fix for Objects=>Runtime change:
import sys
sys.LoadAssemblyByName("System.Windows.Forms")
sys.LoadAssemblyByName("System.Drawing")
sys.LoadAssemblyByName("IronPython")
from System.Drawing import Size
Hello,
One of the design issues
that followed IronPython pretty much since the very beginning was to find
correct place for the two methods we added into the built-in sys module –
sys.LoadAssemblyFromFile and sys.LoadAssemblyByName. The downsides were not
only that these methods didn’t
Hi,
Changing the namespace Object to Runtime, fix the bug. Thank you all for
your support.
Catalin.
- Original Message -
From: "Martin Maly" <[EMAIL PROTECTED]>
To: "Discussion of IronPython"
Sent: Tuesday, January 03, 2006 12:31 AM
Subject: Re: [IronPython] Avalon tutorial
> Yep, as
14 matches
Mail list logo
