.
> Date: Fri, 8 Jun 2012 21:22:47 -0400
> From: tallji...@gmail.com
> To: super24bitso...@hotmail.com
> CC: cplusplus-sig@python.org
> Subject: Re: [C++-sig] Properly copying wrapped classes
>
> It looks like the only way to get a wrapper object is by actually
> in
ut the C++ side code, while the non clone prints out the
python side code.
> Date: Thu, 7 Jun 2012 17:13:55 -0400
> From: jbo...@astro.princeton.edu
> To: super24bitso...@hotmail.com
> Subject: Re: [C++-sig] Properly copying wrapped classes
>
> On 06/05/2012 12:41 AM,
non clone prints out the python side
code.
> Date: Thu, 7 Jun 2012 17:13:55 -0400
> From: jbo...@astro.princeton.edu
> To: super24bitso...@hotmail.com
> Subject: Re: [C++-sig] Properly copying wrapped classes
>
> On 06/05/2012 12:41 AM, Jay Riley wrote:
> > That got rid of the co
On 05/31/2012 08:49 PM, Jay Riley wrote:
I'm having a problem with some python objects derived in python. I have
a Clone method that's supposed to make a full copy of these python
inherited objects, but it isn't working. The problem is my wrapper
class' PyObject* self isn't getting copied, so whe
I'm having a problem with some python objects derived in python. I have a Clone
method that's supposed to make a full copy of these python inherited objects,
but it isn't working. The problem is my wrapper class' PyObject* self isn't
getting copied, so when I use call_method<>(self, "method nam
