Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Gregory Warnes
On Mar 26, 2007, at 3:46PM , Jacob Joseph wrote: > Gregory, thanks for the quick assistance. > > If I manage to press ctrl-c while still in rpy.py:__call__(), I can > get > back to the python shell, It looks like r's signal handler is doing its thing corrrectly, > and get a segfault at exit

Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Gregory Warnes
Hmm. Try this code instead, maybe it'll be slow enough to ensure you can get it while still inside of call(): >> from rpy import r >> r("for(i in 1:1e6) rnorm(1e6)") On Mar 26, 2007, at 3:46PM , Jacob Joseph wrote: > Gregory, thanks for the quick assistance. > > If I manage to pres

Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Jacob Joseph
Gregory, thanks for the quick assistance. If I manage to press ctrl-c while still in rpy.py:__call__(), I can get back to the python shell, and get a segfault at exit from this shell. At other times, it will segfault immediately. Pressing ctrl-c a second time in rapid succession seems with my

Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Gregory Warnes
Hi Jacob, It looks like the event handler code isn't properly setting or resetting the control-c handler. Can you try seeing whether Control C is handled correctly while R itself is processing. IE, exectute: from rpy import r r("for(i in 1:1e6) 1+1") then press Control-C.

Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Jacob Joseph
Linux. Sorry, I didn't even think to include it. -Jacob On 03/26/2007 02:47 PM, Gregory. R. Warnes wrote: > What O/S? > > > > On Mar 26, 2007, at 11:36AM , Jacob Joseph wrote: > >> Hi folks, >> I'm looking for suggestions to correct a crash caused by R. Often, >> upon >> pressing ctrl-C a

Re: [Rpy] R segfault on ctrl-c

2007-03-26 Thread Gregory. R. Warnes
What O/S? On Mar 26, 2007, at 11:36AM , Jacob Joseph wrote: > Hi folks, > I'm looking for suggestions to correct a crash caused by R. Often, > upon > pressing ctrl-C after importing rpy, R segfaults. I need not have yet > accessed rpy for this to occur. Here's a sample: > > *** caught se

[Rpy] R segfault on ctrl-c

2007-03-26 Thread Jacob Joseph
Hi folks, I'm looking for suggestions to correct a crash caused by R. Often, upon pressing ctrl-C after importing rpy, R segfaults. I need not have yet accessed rpy for this to occur. Here's a sample: *** caught segfault *** address (nil), cause 'unknown' Possible actions: 1: abort (with c

[Rpy] R segfault on ctrl-c

2007-03-26 Thread Jacob Joseph
Hi folks, I'm looking for suggestions to correct a crash caused by R. Often, upon pressing ctrl-C after importing rpy, R segfaults. I need not have yet accessed rpy for this to occur. Here's a sample: *** caught segfault *** address (nil), cause 'unknown' Possible actions: 1: abort (with cor

[Rpy] Please submit converters/python wrappers

2007-03-26 Thread Gregory R. Warnes
Everyone: I would like to start bundling additional class converters & python classes with rpy. Please submit converters/wrappers/etc that you've written using the Sourceforge patch site at: http://sourceforge.net/projects/rpy/patches -Greg -

Re: [Rpy] datetime support

2007-03-26 Thread Gregory. R. Warnes
Hi Craig, While rpy does not currently ship with datetime support, this support has been created by other users. Perhaps someone on the list will share their code. -Greg On Mar 25, 2007, at 11:32PM , Craig Brown wrote: > I saw some old email in the archive talking about datetime support

[Rpy] datetime support

2007-03-26 Thread Craig Brown
I saw some old email in the archive talking about datetime support. Does rpy have / plan to have python to R datetime conversion? thanks ...cmb - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Te