On 14 Jun 2012 at 15:01, Wichert Akkerman wrote:
> On 06/14/2012 02:33 PM, Niall Douglas wrote:
> > Do you think that this answer is worth adding to the BPL FAQ?
> > Normally you don't need to derive from Python's Exception object, and
> > indeed in my own custom exception implementations I never
On 06/14/2012 02:33 PM, Niall Douglas wrote:
Do you think that this answer is worth adding to the BPL FAQ?
Normally you don't need to derive from Python's Exception object, and
indeed in my own custom exception implementations I never did so.
However, if this has changed, an FAQ entry is appropri
Do you think that this answer is worth adding to the BPL FAQ?
Normally you don't need to derive from Python's Exception object, and
indeed in my own custom exception implementations I never did so.
However, if this has changed, an FAQ entry is appropriate.
Ideally, a wishlist work item would ma
On 06/14/2012 11:19 AM, Wichert Akkerman wrote:
Hi Jim,
On 06/14/2012 01:02 AM, Jim Bosch wrote:
I suspect the problem is that your custom exception doesn't derived
from Python's built-in Exception base class. Unfortunately, it's
impossible to do that with a Boost.Python wrapped class, but yo
Hi Jim,
On 06/14/2012 01:02 AM, Jim Bosch wrote:
I suspect the problem is that your custom exception doesn't derived
from Python's built-in Exception base class. Unfortunately, it's
impossible to do that with a Boost.Python wrapped class, but you can
get it all done with the Python C API:
n
