Re: [Rpy] [patch] expose R_MissingArg

2009-02-10 Thread Laurent Gautier
Nathaniel Smith wrote: > On Mon, Feb 9, 2009 at 11:07 AM, Laurent Gautier wrote: >> Yes. I would actually put at the rinterface/__init__.py level >> (still at the rinterface level, but this would cut down on C-level >> development time). > > Yeah, IME python wrapping is all about writing the thin

Re: [Rpy] [patch] R 2.7 compatibility fix for rpy_device.c

2009-02-10 Thread Laurent Gautier
Peter wrote: > On Mon, Feb 9, 2009 at 9:06 PM, Laurent Gautier wrote: >> I have no strong preference on the matter. I often get by with whatever >> default the Emacs on the system has, but I can accommodate with no-tabs >> if wished (although now comes The Question: how many spaces ?). >> > > If

Re: [Rpy] [patch] R 2.7 compatibility fix for rpy_device.c

2009-02-10 Thread Laurent Gautier
Nathaniel Smith wrote: > On Mon, Feb 9, 2009 at 1:06 PM, Laurent Gautier wrote: >> I suppose that your have strong arguments for not moving from R-2.7 to R-2.8 >> ? NewDevDesc was a transition entity and has gone away with R-2.8. >> (It's still a moving target, but the target R for rpy2-2.1 by the

Re: [Rpy] [patch] event processing on unix/OS X

2009-02-10 Thread Laurent Gautier
Nathaniel Smith wrote: > On Mon, Feb 9, 2009 at 2:45 PM, Laurent Gautier wrote: >> I couldn't find that one incantation when I looked for it: >> R_runHandlers(R_InputHandlers, R_checkActivity(1, 1)); >> >> I change it to >> R_runHandlers(R_InputHandlers, R_checkActivity(0, 1)); >> because of >> h

Re: [Rpy] [patch] trivial console output fix

2009-02-10 Thread Laurent Gautier
Nathaniel Smith wrote: > It turns out that the new definition of consolePrint (that I wrote, > *cough*) is totally broken -- it tries to write to sys.stdout, and > it's in a module that imports sys, but... there's some code in the > middle that does 'del sys'. So console output just doesn't work ri

Re: [Rpy] [patch] event processing on unix/OS X

2009-02-10 Thread Nathaniel Smith
On Tue, Feb 10, 2009 at 11:39 AM, Laurent Gautier wrote: > Dismantling R_runHandlers is indeed opening interesting perspectives. Quite so. Obviously someone should rewrite R's event loop. Someone else. > Callbacks are the Achilles tendon, I suspect. > I had an independent locking mechanism for f

Re: [Rpy] [patch] trivial console output fix

2009-02-10 Thread Nathaniel Smith
On Tue, Feb 10, 2009 at 1:51 PM, Laurent Gautier wrote: > The callbacks are biting back with this bug as well: an exception should > have been raised when an error occurred (it became obvious while I was > experimenting with rpy_device). > Before devising my own solution I'd be keen on seeing how