similar to: RSPython for Windows: was driving R from Python (calldll?)

Thanks for your help Duncan. Your last comment helped me to figure out what FreeBSD was doing differently than Linux/Solaris. This fix worked on a machine with Python 2.1, R 1.3.1 and FreeBSD 4.1. Here are the details: The pthreads fix: I added '-lc_r' to the PKG_LIBS definition in src/Makevars.in. The FreeBSD 'man pthread' page suggests that adding -pthread to the gcc statement

I didn't see any mention of this in the material on CRAN. The two S.h files define R_problem_buf as a real symbol rather than simply declaring its existence. As a result, a shared library that links two or more files that include this will get duplicate symbol complaints. Since it is not defined elsewhere in the code, someone has to define it. A secondly thing is the documentation for .C()

We have finally configured the R-Java interface as a `regular' R package. This allows R users to create arbitrary Java objects and call any accessible method. It has a reasonably sophisticated mechanism for handling transferring of arguments from R to Java and vice-versa, and allows Java classes to be implemented via R functions. The package and all the documentation is available from

I have finally got around to putting 4 packages on the Omegahat web site for use on Microsoft Windows. The packages are: RDCOMClient - interactive, dynamic access to arbitrary (D)COM objects from within R that allows one to create COM objects from R and call their methods and access their properties without the need to compile any code specific to the COM object. RDCOMServer - facility for

Is there a way to programmatically determine how many arguments a function accepts? In S, one can compute this as length(theFunction) - 1 and determine the parameter names as names(theFunction) due to the representation of functions. (Just in case anyone is thinking of nargs(), that is just for particular calls and does not concern itself with the function definition.)

> From: "Yves Gauvreau" <cyg at sympatico.ca> > References: <Pine.GSO.4.05.10006170711230.12526-100000 at auk.stats> > Date: Sat, 17 Jun 2000 08:41:57 -0400 > Sender: owner-r-help at stat.math.ethz.ch > Precedence: bulk > > This discussion is quite interesting. From the little I know of these issues > may I humbly suggest that parallelism may be the

Sam Rushing's Python extension 'calldll' will supposedly give me access to any DLL, and presumably R.DLL in particular, from Python. I have no experience manipulating DLLs as yet. I am learning Python. I can't find any simple step-by-step instructions on how to get done what I want to do. Does anyone have experience with this? Is there a better way? Of course, one can use

A question for a (experienced) user of the RPython package on linux. I'm trying to call R from python on a linux (Suse 7.3) box. After installing R CMD INSTALL -c RSPython_0.5-2.tar.gz I start python and do: >>> import sys >>> sys.path.append('/usr/local/lib/R/library/RSPython') >>> sys.path.append('/usr/local/lib/R/library/RSPython/Python')

Hi, I'm trying to install RSPython v0.5-4 on a debian machine (woody, testing) but am having the following problem. $R CMD INSTALL -c --library=/usr/lib/R/library RSPython_0.5-4.tar.gz 2>err But then... $python >> import RS Error in .PythonInit() : Error in Python call: values Error in library("RSPython") : .First.lib failed for 'RSPython' Traceback (most recent

Hi Folks, After seeing some tips on the web, I managed to get RSPython-0.7-1 installed with R 2.9.0 (on Ubuntu 8.04). I had to get rid of the extra comma in the PythonPath function in Python.S: .PythonPath <- function(path=NULL, merge = TRUE) { dirSep <- ifelse(R.version$os == "Win32", ";", ":",) (remove last comma before bracket) and I had to manually

Does anyone know if Is there a way to manually install RSPython? I get this error when I try to run the script from my DOS prompt. V:\>R CMD INSTALL -c C:/Users/gene.leynes/Downloads/RSPython_0.7-1.tar.gz * installing to library 'C:/Users/gene.leynes/Documents/R/win-library/2.13' * installing *source* package 'RSPython' ... **********************************************

Hi all, I try to utilize RSPython to invoke Python from R. For me it works pretty fine for basic applications, but I have 3 problems that may be related. (1) I can't load other packages but "standard" ones also when I adjust the PythonPath: > importPythonModule('sys', all=T) NULL > importPythonModule('numpy', all=T) Error in

Hello. I tried to install RSPython on Solaris 5.9. After compiling R with --enable-R-shlib, I try to install RSPython using "R INSTALL --clean RSPython". This led to an error complaining about missing "libutil", wich seems not to exist on Solaris. Therefore I just removed the "-lutil" entry in "configure" and tried to install again. The installation worked

I am very much a beginner at Python and am trying to get RSPython to work for me to solve a specific problem with geocoding addresses using the geopy library for Python (which appears to be an easy way to geocode large numbers of addresses). While I can load up the RSPython library just fine, when I try to load the geopy module using the importPythonModule('geopy') command, I get an error

I can compile RSPython without difficulty, been when I try to load it, I get the error messages below. Also below are some cryptic warnings I get on R boot (in case these are pertinent) and my sessionInfo(). Any help is appreciated. Thanks, Mark Warning messages: 1: In .updateMethodsInTable(fdef, where, attach) : Couldn't find methods table for "conditional", package

Dear colleagues: This summer, the ASA will award a new prize for statistical software. This note is to encourage you to apply or nudge someone you know to apply. The award is for software that contributes to better use of computing in statistical research and applications, written while the applicant was a student. There is a $1,000 prize plus the opportunity to give an invited talk at the

We're starting work on an R package and corresponding S-Plus library to help programmers write software that will work in both systems. Some descriptions and downloadable software are available on the Omegahat web site, at http://www.omegahat.org/SLanguage/ The strategy, as described there, is to be as back-compatible within R and within S-Plus as possible, but provide tools and guidelines

I'm about to commit some changes to the methods package. Before downloading the revised code, note the following. Because the changes involve a revised version of storage for the methods definitions, you will need to re-install any packages that contain method definitions, from their source code. Otherwise the methods will look as if they've disappeared from the generic functions. The

There is a version of the methods package committed today that does dispatch in C for these functions. This should considerably speed up programs that define methods for these functions (specifically, having methods should only marginally affect the existing computations for the same function on basic vectors and objects). This is the first of several steps needed. Not quite all primitives are

I had better mention this one separately, since until it's settled you need a workaround. If you define methods for primitives now, this does NOT create an explicit generic function for, say, "[", so that the original primitive computations still run. This means that the method dispatch has to be turned on for that function somehow else. The proposal is that the library() and