On 22-9-2014 20:28, Chris Angelico wrote:
> On Tue, Sep 23, 2014 at 4:23 AM, Irmen de Jong wrote:
>> This is why Pyro has been using a different (and safe) serializer by default
>> for a while
>> now. You have to plow through the usual security warnings in the docs and
>> make a
>> conscious eff
On Tue, Sep 23, 2014 at 4:23 AM, Irmen de Jong wrote:
> This is why Pyro has been using a different (and safe) serializer by default
> for a while
> now. You have to plow through the usual security warnings in the docs and
> make a
> conscious effort in your code to enable the pickle serializer
On 22-9-2014 19:53, Chris Angelico wrote:
> On Tue, Sep 23, 2014 at 3:47 AM, Irmen de Jong wrote:
>> I've developed Pyrolite (https://github.com/irmen/Pyrolite), a lightweight
>> client
>> library for Java and .NET to gain access to Python servers running Pyro. As
>> such it also
>> contains a c
On Tue, Sep 23, 2014 at 3:47 AM, Irmen de Jong wrote:
> I've developed Pyrolite (https://github.com/irmen/Pyrolite), a lightweight
> client
> library for Java and .NET to gain access to Python servers running Pyro. As
> such it also
> contains a complete pickle and unpickle implementation in the
Hi,
I've developed Pyrolite (https://github.com/irmen/Pyrolite), a lightweight
client
library for Java and .NET to gain access to Python servers running Pyro. As
such it also
contains a complete pickle and unpickle implementation in these languages.
Quite recently I got a pull request to fix a
