Re: [Rpy] initr() creates tempdir

Laurent, is there an example for such a custom cleaner somewhere, or a documentation on the interface? Also, is it possible to obtain the path to the temporary R directory on the python side in order not to delete temporary directories of other, parallel R sessions? I've come across the same is

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

I'm in no way knowledgeable about python (or R) internals, but for me this smells like Rpy putting some parts of it's initialisation into memory areas which are also accessed by other parts of the python interpreter. And that probably shouldn't happen... On 19 May 2011, at 23:18, Thomas Kluyv

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

Done - issue #74 Christian. On 14 May 2011, at 08:37, Laurent Gautier wrote: > Please use the bug tracker on bitbucket. > Otherwise there is a great chance this falls between the cracks. > > On 2011-05-13 17:49, Christian Marquardt wrote: >> Hello, >> >> I e

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

Hmm, I've been building our python (2.7.1) with --enable-unicode=ucs4 which I believe stands for 4-byte Unicode. In any case, Rpy handles (should handle?) the Unicode conversion through python C-API calls which should behave consistently with the way the original python has been build. As I s

Re: [Rpy] More seg faults (Rpy 2.2.0beta3)

I tried your popen script before, but it's running fine - no core dump. I'll might try to compile a debuggable python over the weekend... Chris. On 13 May 2011, at 18:09, Artur Wroblewski wrote: > On Fri, May 13, 2011 at 03:49:49PM +0000, Christian Marquardt wrote: >&

[Rpy] More seg faults (Rpy 2.2.0beta3)

Hello, I experienced seg faults and core dumps related to rpy with several recent versions of rpy, and reported some of them on this list. Here's another one, this time with rpy 2.2.0beta3 (and python 2.7.1) occurring during one of the tests coming with the source code. After unpacking, cd rpy

Re: [Rpy] Segmentation faults with RPy2-2.2.0-alpha4 on Linux and Intel compilers

Gautier wrote: > On 4/5/11 10:08 PM, Christian Marquardt wrote: >> >> Hi, >> >> I reported something very similar for v2.1.9 (see >> >> http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimOkRDv98e5ZcyzmJrzsdYq3%2B6iqAC7_FNk_p53%40mail.gmail.com

[Rpy] Segmentation faults with RPy2-2.2.0-alpha4 on Linux and Intel compilers

Hi, I reported something very similar for v2.1.9 (see http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimOkRDv98e5ZcyzmJrzsdYq3%2B6iqAC7_FNk_p53%40mail.gmail.com&forum_name=rpy-list). With RPy 2.2.0 alpha4, python 2.7.1, numpy 1.5.1, scipy 0.8.0 and R 2.12.1, all compiled with the I

[Rpy] Rpy 2.2.0 and Python 2.5

Hi, the documentation of the current development version (http://rpy.sourceforge.net/rpy2/doc-dev/html/overview.html) states that the minimum requirement for Rpy 2.2 is python 2.5, although development is done on 2.6. As I've got one older system with Python 2.5, I ran into two issues that make Rp

[Rpy] RPy 2.1.9 - segmentation fault after load

Hi, with RPy 2.1.9, python 2.7.1, numpy 1.5.1, scipy 0.8.0 and R 2.12.1, all compiled with the Intel compiler suite (11.1) including MKL, and running on Linux (OpenSuse 11.1 if someone cares), this funny thing happens: >python Python 2.7.1 (r271:86832, Nov 30 2010, 12:31:54) [GCC Intel(R) C++ gcc

Re: [Rpy] RPy 2.1.9 - installation problem with Intel's MKL

Laurent, On Thu, Dec 2, 2010 at 5:58 PM, Laurent Gautier wrote: > Thanks for the patch, however at first sight I am surprised that is it > really working for you. > Wouldn't > '^(?P-Wl.+)$' > be better ? yes, you're probably right... to be honest, I hadn't digged through your code much. I just

[Rpy] RPy 2.1.9 - installation problem with Intel's MKL

Hi, I've run into a minor glitch when trying to install rpy 2.1.9 with R 2.12 and Python 2.7.1 when using Intel'ls MKL.For compiling R, the specification of the MKL libs looks something like this: ... -Wl,--start-group -lmkl_intel -lmkl_sequential -lmkl_core -Wl,--end-group -lpthread ... wher

[Rpy] Rpy2 and automatic conversion of numpy arrays

Hi, once more my apologies if I'm missing the obvious... The rpy2 documentation at http://rpy.sourceforge.net/rpy2/doc-2.1/html/numpy.html#high-level-interface states that the import of the numpy2ri module "alone is sufficient to switch an automatic conversion of numpy objects into rpy2 objects."

Re: [Rpy] RPy 2.1.0rc issue

On Tue, Apr 20, 2010 at 10:05 PM, Laurent Gautier wrote: [...] > locfit = importr("locfit") > > would be recommended (so you are sure of where "locfit" comes from) > > locfit is advertised to accept a /formula/. > I'd suspect that the error is because loc does not implicitly turn strings > into fo

[Rpy] RPy 2.1.0rc issue

Hi, I'm very new to RPy, so I apologize in advance if the question is stupid... In the following (python 2.5.2, R 2.10.1, numpy 1.4.0, rpy 2.1.0rc), the call to R.lm works fine, but a similar call to locfit (from the locfit package at CRAN) throws an error message: --