okay, my last commit today brings python 3.2 support. i ran the regression
on linux on python 2.4, 2.5, 2.6, 2.7 and 3.2 -- they all pass now. i only
need to run it on windows too, and we're done.

that being said -- since py3k is quite a drastic change -- i would love to
get feedback from users running rpyc on python 3.1 and 3.2. i want to hold
the release for a couple of days until we know everything's okay.

by the way -- don't try to mix clients and servers running different
versions of python (2.x with 3.x) -- the object model is too different for
rpyc to bridge, and you'll surely run into lots of bytes/str errors. don't
do it :)


-tomer

-----------------------------------------------------------------

*Tomer Filiba*
tomerfiliba.com     <http://www.facebook.com/tomerfiliba>
<http://il.linkedin.com/in/tomerfiliba>



On Sun, Sep 18, 2011 at 19:21, Tomer Filiba <[email protected]> wrote:

> woohoo! only one more open issue left for 3.2.0 -- the long awaited py3k
> support.
> i already implemented the necessary syntax changes and renamed imports,
> but it's not yet tested and is surely buggy.
>
> but hey -- the release is almost here :)
>
>
>
>
> -----------------------------------------------------------------
>
> *Tomer Filiba*
> tomerfiliba.com     <http://www.facebook.com/tomerfiliba>    
> <http://il.linkedin.com/in/tomerfiliba>
>
>

Reply via email to