Hi, I have converted a few of the core modules to python3. This might be useful to you as you are about to start doing the same. I found the 2to3 tool to be inadequate with many of the modules. netref_3 and vinegar_3 are done and have full nose unit test coverage. Brine has been converted but I just used pickle as I didn't care about security. Some work as also been done on the protocol module, but it is unfinished and has no unit tests.
My branch exists on github.com/Eyecue/rpyc My starting point was a cross between your code and Alex Grönholm's so the directory structure is very similar to your more recent code. I might try merging my work back into your main branch once my stuff is more complete. The layout of this fork is a little chaotic, it contains two versions of the core files, my starting point and the py3 converted version netref.pt and netref_3.py etc. Perhaps not ideal from source control point of view, but I thought the project was dead and for my eyes only. I have also been very brutal renaming stuff, am so no longer compatible with your stuff, alex's or python2, imports paths wont make sense as I was sym linking for convenience and my commit log was for my eyes only :). Other than that it's ok....... (Have also here attached tarball containing just the core key files and their unit tests for your convenience.) Are you planing your releases to be both python2 and 3 compatible, or a separate fork for each? Alastair [email protected] P.S. I couldn't find your email address so I posted here
rpyc_3.tgz
Description: GNU Unix tar archive
