Hello there, I'm looking at using RPy for a production system for a pretty big financial system, so this might not be the last time I'm emailing this list... I can see from the svn log that development is not that quick, but are the developers (people w/ commit access) paying attention?
Well, if nothing else, I'd like to shoot off a little patch that fixes a stupid traceback. Please see [1] for the patch. I ran into this because just typing "r" at the interpreter after "from rpy import r" gives a traceback, which is a pity. It seems this is a problem with a little imbalance of using '.' and '_' in different places. Should be straightforward. I also noticed that my version 1.0.3 of NumPy complained about the use of numpy.get_numpy_include() rather than numpy.get_include() in setup.py (it issued a DeprecationWarning). Not sure what the backwards compatibility concerns for this thing are, but it might be of some use. See [2]. Cheers, Manuzhai [1] http://manuzhai.nl/files/fix-r-version.diff [2] http://manuzhai.nl/files/correct-numpy-include.diff ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
