I am curious to hear whether this is changing much, since the
win32-specific fix proposed has been implemented since 2.0.3
(http://rpy.sourceforge.net/rpy2/doc/html/changes.html#new-features)
You can also see it for yourself here:
http://bitbucket.org/lgautier/rpy2/src/6c793f1f1a37/rpy/rinterface
Look at how I solved that problem. I have no problem with plot window currently.
http://sourceforge.net/tracker/?func=detail&atid=453021&aid=1944503&group_id=48422
On Wed, Jul 22, 2009 at 12:45 AM, wayne jones wrote:
>
> Hi Everyone,
>
> I am trying to run the following simple script to test R
On Wed, Jul 22, 2009 at 2:53 PM, Laurent Gautier wrote:
> Skipper Seabold wrote:
>>
>> Hello all,
>>
>> Are RPy bugs still being accepted on the sourceforge page?
>
> They certainly are.
>
>> I think I found one when trying to do an rlm estimation.
>>
>> I can provide code to (possibly) reproduce;
Skipper Seabold wrote:
> Hello all,
>
> Are RPy bugs still being accepted on the sourceforge page?
They certainly are.
> I think I found one when trying to do an rlm estimation.
>
> I can provide code to (possibly) reproduce; however, the short version
> is this. Given the stackloss data from
wayne jones wrote:
> Hi Laurent,
>
> Thanks for the link describing how to update the R graphics window.
>
> I modified my original script to the following:
>
> ###
> import rpy2.robjects as robjects
> import rpy2.rinterface as rinterface
> import time
> import threadi
Hi Laurent,
Thanks for the link describing how to update the R graphics window.
I modified my original script to the following:
###
import rpy2.robjects as robjects
import rpy2.rinterface as rinterface
import time
import threading
def refresh():
# Ct
