Thanks for a great New Years present!
I'm most interested in what you did to fix the memory issues from
previous versions. I've already found the Compile and Execute(object)
methods on PythonEngine. Are there any other changes that can help to
limit memory footprint when hosting IP?
I found on
Hi all,In my search for the ultimate (or indeed any) IronPython
IDE, I have run across (the free) Visual Studio Express Edition. Can this be
used with Iron Python in the way described earlier in this
list?Thanks,Robert
This message w
Anopther problem: the method PythonEngine.ExecuteFile() throws
System.ArgumentException: Error binding to target method.
at System.Delegate.CreateDelegate(Type type, Object target,
RuntimeMethodHandle method)
It's called from:
>
IronPython.dll!IronPython.Runtime.Ops.CreateDynamicDelegat
Dear All,
Happy new year! I really hope IP can grow up more quickly in 2006. :)
My silly question is how to debug IronPython program. In the MSDN TV,
Jim showed us how to debug IronPython code. But I failed to simulate the
case which Jim demoed. The debugger of VS 2005 didn't locate the
Hi , I am starting to learn and feel IronPython and now porting some py files to IronPython. How should the cStringIO be handled?Antony
___
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
[EMAIL PROTECTED] wrote:
>
> In my search for the ultimate (or indeed any) IronPython IDE, I have
> run across (the free) Visual Studio Express Edition. Can this be used
> with Iron Python in the way described earlier in this list?
>
You can use Visual Studio Express to edit files but the integra
Hello,I compiled the folowing class with "csc"
to csextend.dll
using System;using
System.Collections;
public class Simple{ private int
data; public Simple(int data) { this.data =
""> } public override string
ToString() { return String.Format("Simple<{0}>",
data); }}
When I try to u
The change to fix the memory leak issues was to use dynamic methods instead of
Reflection.Emit which generates non-garbage collectable types & code. There
are some downsides to this in that having a type allowed us to make more
optimizations. If you want more information than that hopefully Ji
We do have part of a cStringIO
implementation - what parts of cStringIO are we currently missing that you
need?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Antony Ma
Sent: Tuesday, January 03, 2006
6:49 AM
To: [email protected]
Subject: [IronPython]
I think in this case Visual Studio may actually be doing the right thing. You
are probably running debug build of IronPython that you built yourself. If you
do that, VS will find that the exception was thrown by the division statement
in IntOps.cs and display that location. At that point, howeve
We have (simple) cStringIO implementation so all you
need is "import cStringIO". If you encounter problems/bugs, please let us know
and we'll fix them. If you do find problems with our cStringIO, you can fall
back to CPython's StringIO module.
Martin
From: [EMAIL PROTECTED]
[mailto:[EMAI
clr.AddReferenceToFile doesn't return any value. It only
adds reference to the .NET assembly. The assembly will then show up in
clr.References tuple.
The way to use the clr.AddReference is the same as the
former sys.LoadAssembly*:
>>>
clr.AddReferenceToFile("csextend.dll")
>>> import Simpl
clr.AddReferenceToFile returns void, so “print a gets
None” is expected.
clr.References could be what you are looking for.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Catalin Lungu
Sent: Tuesday, January 03, 2006
7:58 AM
To: Discussion of IronPython
Subject:
A number of bugs seem to have been introduced with the new assembly
loading code:
First off, my assemblies will no longer load if they're named x.y (for
instance, I was using an assembly that was named Aforge.Imaging). This
will break since the code does a .split('.') to find all the names to
load
Hi Steven,
I am not observing the first and second set of the problems you reported. My
assembly has name c.d.e.dll and adding reference to it works just fine. It
shows up in the References right away also.
>>> import clr
>>> clr.AddReferenceToFile("D:\\Ip\\IronPython\\c.d.e.dll")
>>> clr.Refer
Ok, but I'm not sure why my situation is different. I've tried this over
and over, and I keep getting the same behavior. The References are not
updated until I do it twice, and I can't import my assembly.
Could it be something odd about the assembly (this worked fine in ip
version 0.9.6)? In fact,
Ok, you have right. In clr.Reference I found
"csextend", but when I import "import Simple" the console
return:
Trackback (most recent call last):
File, line 0, in imput
##1
Import Error: No module named Simple
I am sure that the name of the C class is
Simple.
Thanks,
Catalin
- Or
17 matches
Mail list logo
