On Friday, 3 July 2015 10:36:45 UTC+1, Nathann Cohen wrote: > > Helloooooooooooo, > > > Realistically, we don't have a chance of pickling interface objects when > we > > don't have any deeper understanding of the object in the interfaced > system. > > Unless the interfaced system supports pickling natively, which few do. > > Yep yep. > > > So my suggestion would be to define x.dumps() as x.sage().dumps(), that > is, > > just pickle the value in Sage. Doesn't work for the singular(3) example > > since the conversion Singular integers->Sage integers hasn't been > > implemented but at least you get the error immediately and not later > when > > you try to load the object. > At least this will work for (most) GAP objects.
> > Sounds right. Better have an exception now than lost data. > > Is there anybody around who would know how to change that? I don't > feel much at home around pickling and interfaces ^^; > > Nathann > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
