Hello,
I have recently been laid off from a job where a made a lot of good
use of Boost.Python. I would like to give something back (while incidentally
keeping my skills from getting rusty). I have already been following the
boost-python tag on stackoverflow and answering a lot of question
On 05/07/2012 11:30 AM, Adam Preble wrote:
I want to make sure I understand the repercussions.
I understand if I were introducing C++ objects into the Python runtime as
internal references that I would be inviting disaster if I delete them on
the C++ side, but continue to use them on the Python
On 7 May 2012 at 10:30, Adam Preble wrote:
> I want to make sure I understand the repercussions.
>
> I understand if I were introducing C++ objects into the Python runtime as
> internal references that I would be inviting disaster if I delete them on
> the C++ side, but continue to use them on th
I want to make sure I understand the repercussions.
I understand if I were introducing C++ objects into the Python runtime as
internal references that I would be inviting disaster if I delete them on
the C++ side, but continue to use them on the Python side. I don't think
either of us were talkin
Only Python may delete a python managed object. You cannot destroy
any python object explicitly from the C++ side of things.
Solution: allow the python wrapper and C++ instance being wrapped to
detach from one another. That way if the C++ object is deleted, you
zombify the python representation
