William Reade wrote:
I had a similar problem in Ironclad -- needing to get the engine which
called a C# method. Try adding a CodeContext parameter to GetModule
(which gets automagically inserted; no need to change the call from
Python), and then using PythonContext.GetContext to get a
PythonCo
This is great news.
Naturally we are all on tenterhooks waiting for a FePy release targeting
IronPython 2.0.1 - even if it requires Mono 2.4. :-)
All the best,
Michael
Seo Sanghyeon wrote:
FePy seems to be dead, right? Sorry about that. This is a brief status
update. And I could use it late
I had a similar problem in Ironclad -- needing to get the engine which
called a C# method. Try adding a CodeContext parameter to GetModule
(which gets automagically inserted; no need to change the call from
Python), and then using PythonContext.GetContext to get a PythonContext
from the CodeCon
Hello guys,
I have a second use case for embedding IronPython in Silverlight. This
is actually a dynamic application with a C# component that needs to
programattically build a Python module.
Again I have the same problem - imports in Python code fail. I would
have expected that accessing the
Hello guys,
I'm having problems with a C# Silverlight application that hosts IronPython.
First of all, this page
http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting implies that
the following code should load assemblies for the hosted IronPython code:
foreach (string name in
2009/5/9 Seo Sanghyeon :
> 2009/5/9 Jb Evain :
>> Hey Seo,
>>
>> On 5/9/09, Seo Sanghyeon wrote:
>>> 4. There is an IronPython bug that manifests only on Mono due to
>>> newline difference. The symptom is that expressions are not printed in
>>> interactive console. This took some time to debug,
2009/5/9 Jb Evain :
> Hey Seo,
>
> On 5/9/09, Seo Sanghyeon wrote:
>> 4. There is an IronPython bug that manifests only on Mono due to
>> newline difference. The symptom is that expressions are not printed in
>> interactive console. This took some time to debug, but there is a fix
>> now.
>>
Hey Seo,
On 5/9/09, Seo Sanghyeon wrote:
> 4. There is an IronPython bug that manifests only on Mono due to
> newline difference. The symptom is that expressions are not printed in
> interactive console. This took some time to debug, but there is a fix
> now.
>
> http://lists.ironpython.com
FePy seems to be dead, right? Sorry about that. This is a brief status
update. And I could use it later as a changelog. How convinient.
1. I am now testing IronPython with CPython 2.6 standard library. FePy
used 2.4 so far. Be sure to check collections.py issue Dave mentions
here:
http://knowbody.
