Thanks a lot for the comment and discussion. A few of mine below.
Bo Peng wrote:
> The main difference is that rpy does one-way communication, is simpler
> than RSPython, than is easier to use.
>
>
> I am not an expert on RSPython. I tried RSPython and rpy and chose rpy
> for the following rea
> I was wondering
> what is the difference between rpy and RSPython.
The main difference is that rpy does one-way communication, is simpler
than RSPython, than is easier to use.
> So I have a question for you - why rpy instead of RSPython? Have you
> tried both, and can you give a comparison of p
Hi,
(off topic slightly, and a slight flame-bait...).
I don't have an answer or clue to your question, but I have played with
PSPython briefly and it did work somewhat for me (and I have not heard
of rpy until reading this through r-devel), and I was wondering
what is the difference between rpy an
On 1/9/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> How is Rpy calling R? Presumably R is running single-threaded, and the
> problem is likely to be that Rpy is using blocking I/O on the R process
> and hence blocking the GUI callbacks that drive the window.
>
> The not-so-simple answer is n
How is Rpy calling R? Presumably R is running single-threaded, and the
problem is likely to be that Rpy is using blocking I/O on the R process
and hence blocking the GUI callbacks that drive the window.
The not-so-simple answer is not to do it that way. It might be well
sufficient to turn wind
Dear list,
Rpy is a python module that provides python interface to R. The
following simple commands
>>> from rpy import *
>>> r.plot(0)
is supposed to create a window that displays the result of plot(0).
However, we observe that
1. Under *nix, rpy+R+python work as expected
2. Under windows, p
