> The normal R command line is just a program that loads up the core R
> code -- some functions written in C that knows how to evaluate code
> written in R, and wraps a UI around them. rpy2 loads up that same core
> R code, but into a Python process instead. So you can think of it as
> turning your
On Sun, Jul 5, 2009 at 10:18 AM, Daniel Yuan wrote:
> Looking a little deeper, I actually do *not* find an R subprocess when
> I initialize rpy2. I guess I do not understand exactly how rpy2 is
> initializing R without a subprocess.
Ah. Yeah, no subprocess here :-).
The normal R command line is j
>> In conclusion, I don't get it :-)
>
> I am not any better than Nathaniel: without you telling a little
> more of what you are trying to achieve, I am left puzzled.
When I execute 'import rpy2.robjects as robjects', I thought Python
was spawning a subprocess for R. Quitting the child proces
Revision: 746
http://rpy.svn.sourceforge.net/rpy/?rev=746&view=rev
Author: lgautier
Date: 2009-07-05 11:06:04 + (Sun, 05 Jul 2009)
Log Message:
---
edited the news for rpy-1.0.3 binaries and rpy2-2.0.6
Modified Paths:
--
trunk/htdocs/news.data
trunk
monipol wrote:
> On 05/07/2009, at 04:03, Laurent Gautier wrote:
>> monipol wrote:
>>> On 04/07/2009, at 18:18, Laurent Gautier wrote:
I finally patched and built win32 binaries for Python2.6/rpy2.0.6.
2.0.6 does not have user-visible changes compared to 2.0.5, but
since the cod
On 05/07/2009, at 04:03, Laurent Gautier wrote:
> monipol wrote:
>> On 04/07/2009, at 18:18, Laurent Gautier wrote:
>>> I finally patched and built win32 binaries for Python2.6/rpy2.0.6.
>>>
>>> 2.0.6 does not have user-visible changes compared to 2.0.5, but
>>> since the code was patched to let th
Nathaniel Smith wrote:
> On Sun, Jul 5, 2009 at 2:04 AM, Laurent Gautier wrote:
>> (''' q <- function(...) { } ''' is only adding a function q()
>> in the globalenv; baseenv['q']() would still call the original function).
>
> Okay, append 'assign("q", q, envir=.BaseEnv)' to that line (if it
> rea
On Sun, Jul 5, 2009 at 2:04 AM, Laurent Gautier wrote:
> (''' q <- function(...) { } ''' is only adding a function q()
> in the globalenv; baseenv['q']() would still call the original function).
Okay, append 'assign("q", q, envir=.BaseEnv)' to that line (if it
really matters; the goal would be to
Nathaniel Smith wrote:
> Can I butt in for a moment and ask why we'd even want q() not to exit?
> There is (unfortunately) no way to create and destroy multiple R
> sessions, because R doesn't have such a capability. Even if there
> were, I don't see what q() would have to do with it -- the right A
monipol wrote:
> On 04/07/2009, at 18:18, Laurent Gautier wrote:
>> I finally patched and built win32 binaries for Python2.6/rpy2.0.6.
>>
>> 2.0.6 does not have user-visible changes compared to 2.0.5, but
>> since the code was patched to let the win32 build and run the version
>> number was bumped.
10 matches
Mail list logo
