Jason Roberts wrote: > > Greetings rpy2 developers, > > > > I am the primary developer of an open source Python package called > Marine Geospatial Ecology Tools > (http://code.env.duke.edu/projects/mget). These tools perform various > jobs that are useful to marine ecologists. Many of the tools are > designed to be invoked from ArcGIS, a desktop GIS application that runs > on Windows. >
rpy2 works best on UNIX-alikes at the moment. (features are not working on win32). > > To date, we have had good success accessing R using rpy. Thank you very > much for making this package freely available. I can't take those credits: rpy is Walter and Greg's work, with the help of contributors. > But we noted last year > that rpy is no longer being maintained, and rpy2 is the new replacement. Kind of. I started with rpy2 about a year ago, as what I was trying to do did not appear possible with rpy. Rpy is still available, although its development on the slow lane at the moment, I think. > It will be a big job for us to switch to rpy2, so we have been delaying > the switch. In the interim, we've been compiling rpy every time a new R > release has come out. This is probably increasingly risky, so we're > becoming more motivated to make the switch. I am not certain of which way the risk probability stand (compile each time, or compile once and hope for the best). Time will tell. > In addition, there is an > ArcGIS 9.3 / rpy compatibility problem that is pretty inconvenient. > Basically we are wondering if this problem exists with rpy2. > > > > The problem was discussed last year; see > http://sourceforge.net/tracker/?func=detail&atid=453021&aid=2062627&group_id=48422 > > <http://sourceforge.net/tracker/?func=detail&atid=453021&aid=2062627&group_id=48422>. > > In brief: Every time ArcGIS 9.3 runs a Python-based tool, it initializes > a new instance of the Python interpreter in the ArcGIS process > (typically ArcCatalog.exe or ArcMap.exe). The interpreter instance > eventually loads the rpy extension module (e.g. _rpy2070.dll). The > interpreter exits when the tool completes. But this does not cause the > rpy extension module to be unloaded from the process, and when ArcGIS > runs the tool a second time, creating a new Python interpreter, rpy > fails to initialize. > > > > In last year's bug report, lgautier mentioned that "the problem was > fixed a few weeks ago" (i.e. last summer). Is it correct then that this > procedure of initializing the interpreter, using rpy2, shutting down the > interpreter, and so on, can be done indefinitely from a single process > without any ill effects? > May be, may be not. I have not looked at whether the C-level part of rpy2 does what it should regarding the creating and destruction of Python interpreters. You could try with a dummy minimal extension to ArcGIS and tell us. Hoping this helps, L. > > Thanks for your help! And thanks again to you guys for developing this > great reusable software. > > > > Jason > > > > > > / / > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
