On Wed, Feb 24, 2010 at 7:37 PM, James Amundson wrote:
>
> On 02/18/2010 04:24 PM, James Amundson wrote:
>>
[snip]
> I spent some time trying to understand how to tell bjam to add a flag to the
> boost_python link line, but I gave up after about fifteen minutes. With the
> CMake build of boost, it
On 02/18/2010 04:24 PM, James Amundson wrote:
Boost Python seems to be failing to catch and translate C++ exceptions
for me on a BlueGene/P installation. I really don't know what to do
next in debugging the problem, so I would appreciate any advice.
I have finally solved this problem myself -
> Hmmm. I only have one module in my test -- pyexcept. Is the fact that it has
> to link to
> libboost_python enough to cause that problem?
Yes. (It was the motivation for boost::python::throw_error_already_set() ).
Sorry to hear my suggestion didn't help. I hope you'll get help from people
fami
On 02/18/2010 05:19 PM, Ralf W. Grosse-Kunstleve wrote:
Your problem may be that an exception thrown in one .so isn't correctly caught
in another .so.
Hmmm. I only have one module in my test -- pyexcept. Is the fact that it
has to link to libboost_python enough to cause that problem?
In th
Your problem may be that an exception thrown in one .so isn't correctly caught
in another .so.
In the dark past we had problems like this, too. To this day I don't import
extensions
directly, but use a small wrapper function, import_ext(). The essential bit is
sys.setdlopenflags(0x100|0x2)
Boost Python seems to be failing to catch and translate C++ exceptions
for me on a BlueGene/P installation. I really don't know what to do next
in debugging the problem, so I would appreciate any advice.
I have a simple test module, pyexcept
-
