I don't think that rpy takes care of this (and I think that it tries to warn people not to try concurrency). rpy2 has a rudimentary system of locks to prevent bad things from happening if someone is foolish enough to try anyway.
Python has a GIL, so would not go far anyway. ;-) Consider using separate processes, that's the way the Python folks have addressed the issue so far (package 'multiprocessing'). L. On 2012-02-10 10:27, Simon Knapp wrote: > Hi List, > > R is not reentrant, does Rpy take care of this somehow, or is it also > not reentrant? > > Cheers, > Simon > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > rpy-list mailing list > rpy-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rpy-list ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
