Btw, I've committed a fix to SVN for the bug that resulted in this
error message:
NameError: global name 'RuntimeExecError' is not
defined
rather than the more appropriate
RuntimeError: "Couldn't execute the R interpreter."
-Greg
---
Fantastic, it seemed to work like a charm. I also had
to install the pywin32 module. Many thanks to those
who replied!
-Hans
--- Gregory Warnes <[EMAIL PROTECTED]> wrote:
> During the installation of R, there is an option (on
> by default) to
> set the R registry entries. If, for some reaso
During the installation of R, there is an option (on by default) to
set the R registry entries. If, for some reason, this gets
unchecked, it doesn't happen.
In any case, the problem can be solved by properly setting the RHOME
environment variable. The RHOME environment variable should poin
H Nesse wrote:
> Howdy, I ran into a rather odd problem installing rpy
> on one computer (I have used it to great success on
> another). Every time I try and import rpy (in IDLE or
> command line) I get the message "Unable to determine R
> version from the registry. Trying another method."
> This
Howdy, I ran into a rather odd problem installing rpy
on one computer (I have used it to great success on
another). Every time I try and import rpy (in IDLE or
command line) I get the message "Unable to determine R
version from the registry. Trying another method."
This is then followed by a usua
