al builds for .NET 4.
From: users-boun...@lists.ironpython.com [users-boun...@lists.ironpython.com]
on behalf of Seo Sanghyeon [sanx...@gmail.com]
Sent: Wednesday, July 15, 2009 2:43 AM
To: Discussion of IronPython
Subject: [IronPython] FePy status update
Now I updated FePy's NAnt build file to include newly introduced
Microsoft.System.Debugging.dll.
I also found that I need to define CLR2 symbol to compile
Microsoft.Dynamic.dll. Without the symbol it won't compile. What is
the purpose of this symbol?
Sorry for the delay,
--
Seo Sanghyeon
__
On #4 I'm going to check-in the fix today - sorry for the delay!
-Original Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Seo Sanghyeon
Sent: Saturday, May 09, 2009 3:05 AM
To: Discussion of IronPython
Subject: [IronPython]
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
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.
