Hi,
> Maybe you are compiling noddy2 with a
> compiler incompatible to the one used for building Python?
Thanks Hrvoje for the hint! Actually I was linking against the python26.lib, changed to libpython26.a
and it is working. For these tests I was using Dev-C++, the ultimate goal would be to use assembler.
But for the moment, no joy with the assembler (even using libpython26.a), it seems that PyExc_TypeError
and alike are the only culprits, the rest is OK.
(Stefan: Cython looks impressive, I will look at it, if this path I took doesn't work, thanks for the suggestion).
Lee
Hi All,
I am new to Python C/API, I am trying to follow the official docs, but
I am confused about raising and catching exceptions from an extension.
For the example provided at
Extending and Embedding the Python Interpreter
2. Defining New Types
2.1.2. Providing finer control over data attributes
eg I don't seem to be able to catch the exceptions raised by the getsetters functions,
the interpreter will just end up in an ugly crash. Something like:
try:
del mynoddy.last
except TypeError, e:
print "Error: ", e
doesn't work. I understand that PyErr_SetString just sets the error and does not raises the exception.
Am I missing something?
I am using Python ver 2.6.6 on Windows.
Any advice is greatly appreciated,
Lee
Hello eveyone:
we are looking for a Python lead in washington area.
Strong on Python
Strong on OOAD
Worked on high performance web application
Cheers,
Radhika Bauerle.
Leapship, Inc.
radha(a)leapship.com
408.355.8462
