Re: [C++-sig] Passing memory allocated in C++ to Python

On 12.01.2016 13:54, Tony Cappellini wrote: > > > In your something class, the data type returned from allocate_memory() > > needs to be something that Python understands. Since that allocation > > function (member) will be allocating 100s of MB of memory, how will > > this memory map to a Python d

Re: [C++-sig] Passing memory allocated in C++ to Python

>>(https://docs.python.org/3/c-api/memoryview.html). I should have mentioned that I am using Python 2.7 (as part of a group project- others are using Python 2.7 as well). Python 3.x is out of the question at the moment, but the memory view looks like an interesting idea. __

Re: [C++-sig] Passing memory allocated in C++ to Python

> In your something class, the data type returned from allocate_memory() > needs to be something that Python understands. Since that allocation > function (member) will be allocating 100s of MB of memory, how will > this memory map to a Python data type? >>Does it have to be a Python (native) data

Re: [C++-sig] Passing memory allocated in C++ to Python

On 12.01.2016 12:52, Tony Cappellini wrote: > > Stefan, > > > To: cplusplus-sig@python.org > Subject: Re: [C++-sig] Passing memory allocated in C++ to Python > Message-ID: <56945036.8080...@seefeld.name > > > Content-Type: text

Re: [C++-sig] Passing memory allocated in C++ to Python

Stefan, To: cplusplus-sig@python.org Subject: Re: [C++-sig] Passing memory allocated in C++ to Python Message-ID: <56945036.8080...@seefeld.name> Content-Type: text/plain; charset=windows-1252 > Essentially- Python needs access to the return value from a malloc() call. >>Really ? Why ? You say

[C++-sig] Problem with shared_ptr converter in boost 1.60

Dear colleges, I work in a project which makes use of the Boost.python module. Las week we received feedback from some people that was having problems after updating boost from version 1.59 to 1.60. Specifically the problem appears while trying to use a shared_ptr class. Until now, we were regis