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:
Hey Seo,
On 5/9/09, Seo Sanghyeon sanx...@gmail.com 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.
2009/5/9 Jb Evain j...@nurv.fr:
Hey Seo,
On 5/9/09, Seo Sanghyeon sanx...@gmail.com 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
2009/5/9 Seo Sanghyeon sanx...@gmail.com:
2009/5/9 Jb Evain j...@nurv.fr:
Hey Seo,
On 5/9/09, Seo Sanghyeon sanx...@gmail.com 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
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
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
