Re: [IronPython] RPyC and IronPython

2008-05-22 Thread Ronnie Maor
ution for projecting them onto .NET types. > And currently in 2.0 anything which implements IEnumerable will get an > __iter__ method. > > Thanks for the reports! > > -Original Message- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Sanghyeon Seo >

Re: [IronPython] RPyC and IronPython

2008-05-22 Thread Dino Viehland
ill get an __iter__ method. Thanks for the reports! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo Sent: Thursday, May 22, 2008 2:56 AM To: Discussion of IronPython Subject: Re: [IronPython] RPyC and IronPython 2008/5/22 Ronnie Ma

Re: [IronPython] RPyC and IronPython

2008-05-22 Thread Sanghyeon Seo
2008/5/22 Ronnie Maor <[EMAIL PROTECTED]>: > 2) id(obj) in IPy returns System.Int64, which unfortunately doesn't pickle > out of the box, since it's not a python native type. This is clearly a bug. Actually, there already is a CodePlex issue, but it is mistitled. http://www.codeplex.com/IronPython

[IronPython] RPyC and IronPython

2008-05-21 Thread Ronnie Maor
I'm trying to use RPyC (http://rpyc.wikispaces.com), which is a great package for "generic remote control" of remote processes. it basically works, except for small changes I needed to make due to outstanding IPy incompatiblities. wanted to let people know in case you also want to use it (it's rea