>there is something to your liking in beta1.
>
>try:
>
>import rpy2.robjects as ro
>ro.r._dotter = True
>ro.r.dev_off()
Rather than have a toggle, why not have an alternate proxy object - then
you don't polute your new API implementation with legacy support. For
example:
from rpy2 import comp
On Mon, 2008-10-13 at 10:27 +0100, Peter wrote:
> On Mon, Oct 13, 2008 at 10:02 AM, laurent <[EMAIL PROTECTED]> wrote:
> > ...is available for download.
> > - It should build and runs with R-2.7.x, R-2.8.0, and Python-2.4, 2.5,
> > and 2.6.0 on Linux, MacOSX, and win32
>
> Hi Laurent,
>
> I dow
On Mon, 2008-10-13 at 10:51 +0100, Peter wrote:
> Peter wrote:
> >> Does the rpy v1 style r.dev_off() still work in rpy v2?
>
> Laurent replied:
> > Not directly. I have a sketchy attempt at making it possible (will be
> > there for the 2.0 release, still scheduled for November), but it will
> >
Peter wrote:
>> Does the rpy v1 style r.dev_off() still work in rpy v2?
Laurent replied:
> Not directly. I have a sketchy attempt at making it possible (will be
> there for the 2.0 release, still scheduled for November), but it will
> not be the default.
>
>> Personally I
>> much prefer this to r[
On Mon, Oct 13, 2008 at 10:02 AM, laurent <[EMAIL PROTECTED]> wrote:
> ...is available for download.
> - It should build and runs with R-2.7.x, R-2.8.0, and Python-2.4, 2.5,
> and 2.6.0 on Linux, MacOSX, and win32
Hi Laurent,
I downloaded the rpy2-2.0.0b1.tax.gz file and I tried this on MacOSX
wi
...is available for download.
- It should build and runs with R-2.7.x, R-2.8.0, and Python-2.4, 2.5,
and 2.6.0 on Linux, MacOSX, and win32
- There are no win32 binaries (my machine with winXP is currently
unavailable), and no MacOSX binaries (I do not have easy access to
MacOSX).
- The documentat
