Okay now this is getting interesting. I assumed that the warning was about
the child class, but I'm not sure. A bit of info: The parent C# class is
called Object. I did the override on on __reduce_ex__ as you suggested
but trying to pickle still produced the same error:
Type 'IronPython.NewTypes.
Ahh, that sounds like a bad bug, but I think I know what's causing it - we're
hitting the new.NET serialization support because __reduce_ex__ is now defined
for you :) Can you add an override that dispatches __reduce_ex__ to the object
version, eg:
def __reduce_ex__(self, *args):
return ob
Thanks for the heads up, however trying to use cPickle, I still get the
error saying that the child class is not marked as serializable..?
On 10/7/08, Dino Viehland <[EMAIL PROTECTED]> wrote:
>
> I would strongly encourage you to use cPickle or pickle instead of .NET
> serialization. In 2.0 all .
I took a look and we're spending most of our time doing old instance/old class
accesses. If they used new-style classes it would probably run faster -
although CPython might as well :) It seems like a good chunk of that is coming
from __eq__/__cmp__ on the old-style classes - and w/ new-style
I would strongly encourage you to use cPickle or pickle instead of .NET
serialization. In 2.0 all .NET serializable types can also be pickled - they
define __reduce_ex__ which handles this.
First off we should be setting the serializable bit on subclasses that are
serializable - that's just a
Antonio Cangiano wrote:
Hello,
I tried IronPython Studio and found fundamental flaws that make
programming with it far from enjoyable. Amongst the annoyances are the
lack of automatic indentation and the fact that the IntelliSense fails
to propose a list of properties for a given control. Mor
I think you are right. Not using the slice operator doesn't give the wrong
output anymore.
Take a look at the implementation it's clear that this doesn't work like
this because the list is copied in 3 steps and the lock is released in
between.
this means that concurrent slice updates results in lo
Hi,
You are right it is not mature. I use it, because the editing and project
handling is ok. I have obstructed a lot features in order to have it work:
- The project management is good as usual.
- The genereated code is not good, so I have obstructed it too.
- The editing is ok
- Intellisense i
