Re: Pyro 4.20 serpent serializer issues

On 09/06/13 01:38, Irmen de Jong wrote:
:
> Decimals are encoded as a literal string (because otherwise you will lose precision).
> The receiver however needs to 'know' this and will have to convert the string back to a
> decimal.Decimal. Similarly, datetime.datetime are encoded as a ISO formatted date+time
> string, and the receiver will have to convert it back explicitly (if desired).
:
> The key issue here is that when not using pickle, you probably will have to redesign
> your remote method contracts if they depend a lot on custom types on both ends. If you
> stick to Python literals mainly, the pain will be a lot less or even non-existent...

Hi Irmen,
Just to be sure I understand correctly, does this mean that in Pyro 4.20
(with the default serializer), a method returning a decimal.Decimal will
return a string when called remotely via Pyro?

Cheers,
Éric


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev