Peter wrote:
> On Tue, Dec 2, 2008 at 11:50 AM, Marcos Silva <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> I made the changes suggested.
>>
>> - I created a R_HOME variable in windows with value "C:\Program
>> Files\R\R-2.8.0"
>> - "import win32api" is OK in my Python installation
>>
>> From R I get:
>>
>>> Sys.getenv("R_HOME")
>> R_HOME
>> "C:\\PROGRA~1\\R\\R-28~1.0"
>
> That looks to me like a Windows 8.3 shortened path (no spaces). Note
> that these names are machine specific - there is no guarantee that
> "C:\Program Files" is always "C:\\PROGRA~1".
>
> This may be fine - what happens if you try this in explorer?
>
>>> R.home()
>> [1] "C:\\PROGRA~1\\R\\R-28~1.0"
>>
>> May I have to change this too?
>
> That matches your environment variable.
>
>> Having made the changes suggestet I tryed to do the test of RPy2 without
>> success... I got:
>>
>> PythonWin 2.5.1 (r251:54863, May 1 2007, 17:47:05) [MSC v.1310 32 bit
>> (Intel)] on win32.
>> Portions Copyright 1994-2006 Mark Hammond - see 'Help/About PythonWin' for
>> further copyright information.
>>>>> import rpy2.tests
>> Traceback (most recent call last):
>> File "<interactive input>", line 1, in <module>
>> File "C:\Program Files\Python25\Lib\site-packages\rpy2\tests.py", line 3,
>> in <module>
>> import rpy2.robjects.tests
>> File "C:\Program
>> Files\Python25\Lib\site-packages\rpy2\robjects\__init__.py", line 12, in
>> <module>
>> import rpy2.rinterface as rinterface
>> File "C:\Program
>> Files\Python25\Lib\site-packages\rpy2\rinterface\__init__.py", line 52, in
>> <module>
>> raise RuntimeError("Unable to locate R.dll within %s" % R_HOME)
>> RuntimeError: Unable to locate R.dll within C
>
> This is the same error as before - which to me suggests a bug in how
> rpy2 is using R_HOME. I suspect its something along the lines of a
> bit of code expecting a list of all the R installations found (there
> could be more than one) and taking the first, but instead is taking
> the first letter of the string for the only R installation.
That seems to be the case.
The code evolved from expecting having R_HOME defined to automagically
guessing it from the system call 'R RHOME'... and that early mechanism
was broken in the process (and this was not tested).
An immediate workaround is to put the right R in the path, and a fix
should appear a little later.
Thanks for tracking that one down,
Laurent
> Peter
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> rpy-list mailing list
> rpy-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rpy-list
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
