On Tue, Feb 10, 2009 at 1:51 PM, Laurent Gautier <lgaut...@gmail.com> 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 packages such as
> pygtk are doing things.
I'm pretty sure pygtk pretty much just sticks something like this
after each call into python:
if (PyErr_Occurred()) {
printf("Unhandled exception!\n");
PyErr_Clear();
}
(Maybe calling PyErr_Print() instead if you fiddle a magic debugging
envvar or something.) For things like the console print callbacks,
it's unclear that there's anything better one *can* do...
-- Nathaniel
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list
