rpyc not detected

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install PyScripter 1.9.9.7 and Python 2.6.2
2. Install rpyc 3.0.6
3. try to set Remote Python engine

What is the expected output? What do you see instead?
PyScripter says :
the Rpyc module is not available. but it is available.
import rpyc works !

What version of the product are you using? On what operating system?
PyScripter 1.9.9.7
Python 2.6.2
rpyc 3.0.6
Windows XP SP2

Original issue reported on code.google.com by sebastie...@gmail.com on 10 Aug 2009 at 11:34

[GoogleCodeExporter]

OK this is just a WAG,  but I noticed that earlier documentation always 
imported rpyc 
using a capital R,  in all the examples.  Indeed if you install rpyc in python 
2.6 
and attempt to 
import Rpyc
it fails.  But 
import rpyc
succeeds.  Inside the menu documentation it always refers to module Rpyc and 
not 
rpyc.  Is it possible that the issue is as simple as a case sensitivity on the 
module 
name?

Just speculation.

Original comment by mattc...@earthlink.net on 24 Sep 2009 at 6:07

[GoogleCodeExporter]

I have make a test by renaming rpyc by Rpyc and it simply works !
So I think PyScripter must try to import Rpyc (old module) and if it fails, try 
to
import rpyc (new module).

Don't forget that python is case sensitive

Original comment by sebastie...@gmail.com on 24 Sep 2009 at 6:44

[GoogleCodeExporter]

I'm having a similar issue when I try to "import Rpyc" (case-sensitive).

Also, I have downloaded and installed rpyc 3.0.7
and PyScripter 1.9.9.7 and Python 2.6.2
and Python paths are setup for Python26

Message File Name   Line    Position    
Traceback               
    <module>    <module1>   1       
    <module>    C:\Python26\lib\site-packages\Rpyc\__init__.py  35      
exceptions.ImportError: No module named rpyc.core               

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

when I run "import rpyc" (case-sensitive):

Message File Name   Line    Position    
Traceback               
    <module>    <module1>   1       
exceptions.ImportError: No module named rpyc                

Original comment by tradigi...@gmail.com on 29 Sep 2009 at 11:09

[GoogleCodeExporter]

Hum... Yes I'm sorry, I have tried to rename the new rpyc module in Rpyc but my 
test
failed. My last comment was a mistake.
tradigital is right.
the problem is more complicated, since rpyc 3.x module is a complete redesign, 
so
it's not just a case sensitive problem.

Original comment by sebastie...@gmail.com on 30 Sep 2009 at 6:52

[GoogleCodeExporter]

OK, yesterday I tried a couple of different things and still no luck.  I had an 
error
saying rpyc was looking for a module named core.  There isn't a core module in 
the
latest installation nor is there on in an earlier installation I tried.  

Today i'm on another machine and I installed rpyc-3.0.7.win32.exe for PyScripter
1.9.9.7 running Python26.  This is a fresh install of rpyc with no previous 
versions
installed.  

I get a PyScripter error when I try to switch the Python engine to Remote from 
the
GUI menu.  It says 

"The Rpyc module is not available.  To use the remote Python Engine download 
Rpyc..."

When I do an import rpyc:

*** Python 2.6.1 (r261:67517, Dec  4 2008, 16:51:00) [MSC v.1500 32 bit 
(Intel)] on
win32. ***
*** Internal Python engine  is active ***

Original comment by tradigi...@gmail.com on 30 Sep 2009 at 4:56

[GoogleCodeExporter]

PyScripter 1.9.9.7 cannot use rpyc 3.x because rpyc has been redesigned since 
Rpyc 2.6.
rpyc 3.x has a core module
so to make rpyc 3.x working with PyScripter, PyScripter need to be patched

Original comment by sebastie...@gmail.com on 1 Oct 2009 at 6:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Forthcoming version 1.9.9.8 uses a bundled version of rpyc 3.07 which does not
interfere with other rpyc installations and does not require a separate 
installed.

Original comment by pyscripter on 2 Jan 2010 at 1:22

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by pyscripter on 30 Sep 2010 at 3:05

• Added labels: Type-Defect