On Wed, Apr 06, 2005 at 03:10:30PM -0400, Brad Clements wrote:
On 5 Apr 2005 at 16:48, Daniel Veillard wrote:
and what happens when 2 threads use libxml2 python bindings. Parsing of A
fails because parsing of B generated and error. No this is more complex
than that, really.
Somewhat
Daniel Veillard wrote:
The 'PyErr_Occurred()' function will return 1 since the (python) error
callback raised an exception that was not yet dealt with.
With the above hack, the example of the OP indeed generates a stack trace
(a TypeError as the string in the 'raise' expression is malformed).
Daniel Veillard wrote:
Okay, could you or Stefan bugzilla this, we don't have a complete solution
(as the error will have to be asynchronously raised back when exiting the
C layer back into Python) but it seems it would be simpler than what I first
expected.
Ok, will do.
Stefan
Daniel Veillard wrote:
Make this a 'void *' normally set to 'NULL', and then abort the normal
processing if it is != NULL. Wrapper code may then tunnel any data through
it.
and what happens when 2 threads use libxml2 python bindings. Parsing of A
fails because parsing of B generated and error.
Whilst experimenting with the Python bindings I noticed that exceptions
are not propagated when using registerErrorHandler(). If I run the
following I get the error message:
/etc/passwd : failed to parse.
However, there is no Traceback for the raise. Is this correct?
import libxml2
On 31 Mar 2005, at 22:43, Daniel Veillard wrote:
On Thu, Mar 31, 2005 at 10:25:41PM +0100, Andrew McDermott wrote:
Whilst experimenting with the Python bindings I noticed that
exceptions
are not propagated when using registerErrorHandler(). If I run the
following I get the error message:
I like cheeseAndrew McDermott [EMAIL PROTECTED] wrote:
On 31 Mar 2005, at 22:43, Daniel Veillard wrote: On Thu, Mar 31, 2005 at 10:25:41PM +0100, Andrew McDermott wrote: Whilst experimenting with the Python bindings I noticed that exceptions are not propagated when using registerErrorHandler().
On Thu, Mar 31, 2005 at 10:58:33PM +0100, Andrew McDermott wrote:
Isn't it the case that the calling sequence starts within Python so it
should be possible to return an error indication?
I don't see how.
Daniel
--
Daniel Veillard | Red Hat Desktop team http://redhat.com/
[EMAIL
On Thu, Mar 31, 2005 at 02:19:47PM -0800, Ron Ohmer wrote:
Why was I unsubscribed?
all the out of context mails, however if you have a rational explanation
for your last 5 mails about cheese I may re-add you.
Daniel
--
Daniel Veillard | Red Hat Desktop team http://redhat.com/
[EMAIL
On 31 Mar 2005, at 23:19, Daniel Veillard wrote:
On Thu, Mar 31, 2005 at 10:58:33PM +0100, Andrew McDermott wrote:
Isn't it the case that the calling sequence starts within Python so it
should be possible to return an error indication?
I don't see how.
OK, I think I see the problem...
So the C
10 matches
Mail list logo
