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 API
for creating and destroying
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.
>
> The win32 binary
> I have just added something in the documentation for 2.1-dev
> http://rpy.sourceforge.net/rpy2/doc-dev/html/callbacks.html#clean-up
> That will hopefully be enough to get you started.
Still no joy:
xn...@work:~> python
Python 2.5.2 (r252:60911, Nov 26 2008, 00:44:29)
[GCC 4.0.1 (Apple Inc. buil
Hi,
Since I was at it, I also worked on getting the 2.1-dev version to build
and (somehow) run on win32.
A binary for today's snapshot is currently on bitbucket:
http://bitbucket.org/lgautier/rpy2/downloads/rpy2-2.1.0a04072009.win32-py2.6.msi
Note that although rpy2-2.1-dev is reasonably stable
Hi,
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.
The win32 binary and source can be found on sourceforge, the source is
