On Sun, Oct 18, 2009 at 4:05 PM, Laurent Gautier <lgaut...@gmail.com> wrote: >>> >>> Ideally I'd like rpy2 to map "arg_name" (in Python code) to either >>> "arg_name" or "arg.name" (when talking to R) as appropriate for >>> the function concerned, but raise an error if both possibilities are >>> defined. That way I continue to use the simple substitution when >>> writing R calls, and only have to worry about these very rare corner >>> cases when due to ambiguity the naive way should raise an exception. >>> I don't know enough about R's introspection to say if this idea is >>> realistic or not. > > The thread was useful, and lead to improvements. > > rpy2-2.1dev now has a sort-of-cached conversion > mechanism (minimizing the hit of performance that converting at each call > would have). Moreover the caching is safe, as it will throw an exception in > the function has a signature that cannot be translated safely. > > http://rpy.sourceforge.net/rpy2/doc-dev/html/robjects.html#functions
That sounds great :) Peter ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list