[C++-sig] C++ destructor calling of boost.python wrapped objects

[Gabor Kovacs]

Dear All,

does boost.python provide any guarantee when the C++ destructor of a
wrapped object is called considering the moment of reaching the zero
reference count of the python object? I am concerned about a C++
object that does some I/O (file close) at its destruction.

I mean:

A=MyBoostPythonObject()
del A # Is the C++ destructor of MyBoostPythonObject called here?

Thanks,
Gabor