hrrm... try erasing all .pyc files, and make sure you renamed every "rpyc" to "rpyc3" in rpyc3's package.
-tomer An NCO and a Gentleman On Wed, Oct 20, 2010 at 09:55, Reenen Laurie <[email protected]> wrote: > Apologies for my n00bness, but I've now got Rpyc and a folder called > rpyc3. > > I am trying to run server.py from the http://rpyc.wikidot.com/demo:chat > example (the actual code)... > > This line: > from rpyc3 import Service, async > > gives this traceback: > Traceback > <module> D:\PythonProjects\ChatDemo\server.py 2 > <module> I:\PORTAB~1.1\App\lib\site-packages\rpyc\__init__.py > 35 <----- This is the path to rpyc 2.6, and not rpyc3. (except > it's Rpyc, but maybe windows is just funny) > ImportError: No module named rpyc.core > > > Am I installing the package wrong? (I am *very* noob at python) > > What I did was download it and extract it to I:\PORTAB~1.1\App\lib > \site-packages\rpyc3. Is there another step to installing a package? > > Regards, > -Reenen > > > > On Oct 19, 5:19 pm, tomer filiba <[email protected]> wrote: > > well, in the 2.xx branch, the package was named "Rpyc", while in 3.xx > it's > > named "rpyc" > > so if you're not using windows, the file system is case-sensitive, and > then > > it's okay. > > > > if not, just rename the "Rpyc" to, say "rpyc2", and change the imports in > > pyscripter to "import rpyc2", > > or rename "rpyc" to "rpyc3", and maybe you'll have to fix some imports in > > the rpyc code itself. > > > > -tomer > > > > An NCO and a Gentleman > > > > > > > > On Tue, Oct 19, 2010 at 13:37, Reenen Laurie <[email protected]> wrote: > > > I got portable python for me (mostly because I am not a "super user" > > > at work, and don't have admin rights) for Python 3. > > > > > On this, rpyc 2.6 is included for PyScripter to use (or that's how I > > > understand). But *I* want to do stuff with services and higher levels > > > of security... > > > > > Is rpyc backward compatible... if not, can I have 2 installed on the > > > same system? > > > > > Regards, > > > -Reenen >
