Pyrolite 1.11, was: Re: Pyrolite 1.10 released (bug fixes related to Python3 and datetime)

Irmen de Jong <[email protected]>
Newsgroups gmane.comp.python.pyro
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-6-2013 14:23, Irmen de Jong wrote:
> Get the new version (1.10) at: http://irmen.home.xs4all.nl/pyrolite/
> 
> NOTE: this version of Pyrolite still only talks Pyro protocol version 44 (used by 
> Pyro up to but not including 4.20). Support for Pyro 4.20+ (protocol version 45+) 
> will appear in a later version of Pyrolite.

Well, it's now Pyrolite 1.11, and support for Pyro 4.20 (protocol version 45) has been
added.

You'll need to set the protocol version in the Config.PROTOCOL_VERSION property in
your java or .net code. It still defaults to 44, but if you set it to 45, you can talk
to Pyro 4.20.
You need to tell Pyro to use the pickle serializer though. Support for the serpent
serializer (the new default in Pyro) is planned for a future Pyrolite version.

(Note that telling Pyro to use pickle again, will bring back the security issue with
that. So it is still not advisable to use this over an unsecure network.)


Enjoy,

Irmen de Jong

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRyIkGAAoJEHC9o7RHFlf2bYAH/iDK6WpsnFLeHEvU8ZDOmnUt
12va/h7F8CPZRcpA2sHmUWD1a6f8EEj9unWMJm9v1sRy1VJ8XR1vv7cOmecFYOK6
pypQZyU0r2dJq7UfvAv8axvAa1nKwd/1pRjHnz0nONjOEtgzeWABtNyWkyosnrs1
rm3mYVRsWQkm06yu9KIA/EY3NaLvenaTrd9/+CixfNDImAx9BYtQOvJ2PfW8CMLF
EkHi0kuddm46vS4NyektFh4BE/qHhCpwaHdBEynY+gCclNntKwuVbUO9Fgam7g8Q
zHYsWxQrok5UqI9ToKok2kXWKq47MU2ACGoxX+5Htw7JmFI5t4O5aVa1VmZVDJw=
=Qb7Z
-----END PGP SIGNATURE-----

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

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.