[IronPython] memory leak in IP 2.0.1

Hello, I host ironPython in c#. It worked well. I changed from 1.1.2 to 2.0.1 and now I have a memory leak. I do not know why. Any idea? I do not know the working of DLR but is there a GenerateCodeSnippet option in IP2.0.1 too? Perhaps it causes the memory leak. Thanks, Zoltan

Re: [IronPython] memory leak in IP 2.0.1

This was response from Dino a couple of emails ago. Direct quote ust some comments on this as there’s a few issues intertwined here: 1. Optimized code – this is currently the default and part of the original problem. If you execute code in “optimized” mode we generate an uncollectible

Re: [IronPython] memory leak in IP 2.0.1

There is a bug item for this memory leak issue http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=20399 2009/3/23 Zsidó Zoltán zsi...@innodev.hu Hello, I host ironPython in c#. It worked well. I changed from 1.1.2 to 2.0.1 and now I have a memory leak. I do not know why. Any

Re: [IronPython] Creating Dynamic Assemblies from IronPython 2.6

Do you actually need MakeOrAdd or would the factory that takes multiple method infos be good enough? I'm just reluctant to open up the ability to modify any built-in function. -Original Message- From: users-boun...@lists.ironpython.com [mailto:users- boun...@lists.ironpython.com] On

[IronPython] Two Problems with sys.argv and compiled scripts

Problem #1 I know this is a know issue, but my google-fu has been able to uncover the solution. When I compile my script into an exe , sys.argv get sets to ' '. Using SharpDevelop and Ironpython 2.0.1 #Program.py # import clr clr.AddReference('mscorlib') clr.AddReference('System') import sys

Re: [IronPython] Creating Dynamic Assemblies from IronPython 2.6

I seem to recall that in Seo's original code, MakeOrAdd was used to build up the overloads over time as user code asked for additional method signatures for the same method name. This could presumably be simulated by replacing the method group in Python with a new method group that contained all

Re: [IronPython] Creating Dynamic Assemblies from IronPython 2.6

Maybe we could add a BuiltinFunctionBuild which provided this functionality. Then as long as the creator holds onto the BFB they can continue to mutate the function w/o allowing anyone else to. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of

Re: [IronPython] Two Problems with sys.argv and compiled scripts

Bruce Bromberek wrote: So if I follow your lead at http://www.voidspace.org.uk/ironpython/custom_executable.shtml it looks like I need to modify this code to call my complied DLL instead of the pythonsource code? string path = Path.Combine(

Re: [IronPython] Creating Dynamic Assemblies from IronPython 2.6

I've been thinking about whether that functionality is really needed. C doesn't support function overloading, so presumably there would only ever by one signature per name? I'll have to see if CPython supports that. - Jeff 2009/3/23 Curt Hagenlocher c...@hagenlocher.org: I seem to recall that

Re: [IronPython] Creating Dynamic Assemblies from IronPython 2.6

It's not quite that straightforward with p/Invoke though -- it can be *very* convenient to define multiple overloads for the same C function with different signatures. Consider the GetPrinter function and the different versions of the PRINTER_INFO_x structure it can deal with: