On Tue, 2008-10-14 at 16:39 +0100, Peter wrote:
> > Not completely, but I clearly overlooked the fact that such backward
> > compatibility through import statements are common practice in Python.
> > That's an interesting suggestion from Andrew... let me think on how I
> > can tie that together.
> Not completely, but I clearly overlooked the fact that such backward
> compatibility through import statements are common practice in Python.
> That's an interesting suggestion from Andrew... let me think on how I
> can tie that together.
>
> I am also seeing two separate points here:
> - provide
On Tue, 2008-10-14 at 10:57 +0100, Peter wrote:
> Laurent wrote:
> >>try:
> >>
> >>import rpy2.robjects as ro
> >>ro.r._dotter = True
> >>ro.r.dev_off()
>
> Andrew wrote:
> > Rather than have a toggle, why not have an alternate proxy object - then
> > you don't polute your new API implementation
Laurent wrote:
>>try:
>>
>>import rpy2.robjects as ro
>>ro.r._dotter = True
>>ro.r.dev_off()
Andrew wrote:
> 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 compat as
>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: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[
Uninstalling is surely not needed:
rpy anr rpy2 can coexist peacefully.
2008/10/9 Srikanth <[EMAIL PROTECTED]>:
> Thank your for the clarification. I tried the old way of replacing a dot
> with an underscore but it didn't work. Now I understand why. I moved back
> to using RPy 1.x because of
Thank your for the clarification. I tried the old way of replacing a dot
with an underscore but it didn't work. Now I understand why. I moved back
to using RPy 1.x because of my problems, but am going to re-install RPy 2.xx
and try the solution.
Thanks again for both the answer and for your work o
2008/10/9 Peter <[EMAIL PROTECTED]>:
>>> r.dev.off()
>>> ...
>>> LookupError: 'dev' not found
>>
>> Python is not R. The dot ("."), like in a large number of other
>> language, has a particular semantic meaning and therefore is
>> not a valid character for variable names.
>>
>> r['dev.off']() is wh
>> r.dev.off()
>> ...
>> LookupError: 'dev' not found
>
> Python is not R. The dot ("."), like in a large number of other
> language, has a particular semantic meaning and therefore is
> not a valid character for variable names.
>
> r['dev.off']() is what you are looking for.
Does the rpy v1 style
On Wed, 2008-10-08 at 16:49 -0500, Srikanth wrote:
[...]
> -
> However, when I run the equivalent code via RPy in a Python console,
> -
> import rpy2.robjects as robject
Greetings,
I have installed (from source) the version rpy2 v2.0.0a3 of RPy. My system's
configuration is:
Python 2.6 Python 2.6 (r26:66714, Oct 8 2008, 10:27:48)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2 (installed from source)
NumPy 1.20 (also installed from source).
I found that I am unab
13 matches
Mail list logo
