Hi Owen,
As far as I know if you want to compile a python code you could use:
clr.CompileModules(.). Or you could use the pyc.py provided in the
IronPython2.0 Samples download.
ipy.exe pyc.py /main:winforms_hw.py /target:winexe which will produce a
winforms_hw.dll as well. I'm not sure if you
That looks like it's removing that memory leak. I'm not positive
that's the one we're having in our production code, but it certainly
can't hurt.
On Nov 25, 5:37 am, Dino Viehland wrote:
> My guess here (I'm on vacation so I haven't tried this) is that some
> exception info
> is not getting cle
This is an automated email letting you know that sources
have recently been pushed out. You can download these newer
sources directly from
http://ironpython.codeplex.com/SourceControl/changeset/view/61769.
MODIFIED SOURCES
$/IronPython/IronPython_Main/Src/Tests/modules/misc/_warnings_t
I am attempting to upgrade a component from iron python 1.1 to 2.6 that
was previously using the PythonProvider to compile python code into a
.NET assembly. It looks like this is no longer present in 2.6. Is this
correct? Are their any plans to resurrect it? The biggest difficulty I
am facing i
Hello,
We are experiencing the problem that is mentioned in this post using
IronPython 2.6 RC 2 but are un-able to un-reference the associated
assembly. I am getting the following error:
Error 2 Unknown build error, 'Cannot resolve
dependency to assembly 'Microsoft.Script
My guess here (I'm on vacation so I haven't tried this) is that some exception
info
is not getting cleared -
ExceptionHelpers.DynamicStackFrames = null;
In the catch block will probably fix it although we should probably
do this ourselves.
> -Original Message-
> From: users-boun...@l
