me
> examples. I'll keep it in mind if I ever have a list of large arrays to
> process for which creating a numpy array first is not desirable.
> - Tom
>
>
> On Tue, Jun 18, 2013 at 6:36 AM, Egor Zindy wrote:
>>
>> Dear all,
>>
>> after some code cl
emaps-for-working-with.html
Any comments appreciated.
Kind regards,
Egor
On 9 June 2013 09:20, Egor Zindy wrote:
> Thanks Tom,
>
> before we ship it, I'd love to have some feedback on the new ARGOUT_VIEWM
> type.
>
> I used to create my managed arrays
Thanks Tom,
before we ship it, I'd love to have some feedback on the new ARGOUT_VIEWM
type.
I used to create my managed arrays using
PyObject* cap = PyCObject_FromVoidPtr((void*)(*$1), free);
but since this function is deprecated, and because of Bill's background
work to bring numpy.i up to
Hi Ralf,
Your post comes just on time! I implemented the memory managed arrays and
noticed a serious problem with my capsule creation code (post I sent to the
list about the update on the 12th of March in reply to Bill Spotz "Request
code review of numpy.i changes"). For some reason, the code I wr
ase there is any other cleanup code to
> execute.)
>
> On Aug 9, 2009, at 6:17 AM, Egor Zindy wrote:
>
>> Hello list,
>>
>> this is my attempt at generating python exceptions in SWIG/C using the
>> errno mechanism:
>>
>> http://www.scipy.org/Cookbook/S
Hello list,
this is my attempt at generating python exceptions in SWIG/C using the
errno mechanism:
http://www.scipy.org/Cookbook/SWIG_NumPy_examples#head-10f49a0f5ea6b313127d2ec5ffa1eaf1c133cb22
Used together with numpy.i, this has been useful for notifying (in a
pythonic way) memory allocation
it took your vacation, but you helped me spend
> mine the way I wanted to (successful programming, hehe).
Don't mention it! I call that a "productive" holiday ;-)
Regards,
Egor
>
> cheers,
> Rich
>
> On Fri, Jan 9, 2009 at 7:05 AM, Egor Zindy wrote:
> > Hello R
Hello list,
I've moved my wiki to the scipy cookbook:
http://www.scipy.org/Cookbook/SWIG_Memory_Deallocation
For the time being, the listed example files are still stored on the google
code SVN, but these could easily be moved if necessary.
I've also just finished adding an ARGOUTVIEWM_ARRAY2 ex
Hello list,
just a quick follow-up on the managed deallocation. This is what I've
done this week-end:
In numpy.i, I have redefined the import_array() function to also take
care of the managed memory initialisation (the _MyDeallocType.tp_new =
PyType_GenericNew; statement). This means that in %
Christopher Barker wrote:
> thanks! good stuff.
> It would be great if you could put that in the numpy (scipy?) wiki
> though, so more folks will find it.
>
> -Chris
>
Hello Chris,
no problems, you are absolutely right, this is where the documents will
have to eventually end up for maximum vi
Egor Zindy wrote:
> Dear List,
>
> after I tried to write a simple ARGOUTVIEW_ARRAY1 example (see
> http://code.google.com/p/ezwidgets/wiki/NumpySWIGMinGW#A_simple_ARGOUTVIEW_ARRAY1_example
>
> ), I started wondering about memory deallocation. Turns out a few
> clever peopl
,
Egor
Søren Nielsen wrote:
> Hi Egor,
>
> Thanks for a very nice tutorial! Have you tried doing manipulations
> with 2D arrays?? or do you know how to tackle it?
>
> Regards,
> Soren
>
> On Fri, Nov 14, 2008 at 12:32 AM, Egor Zindy <[EMAIL PROTECTED]
>
Hello list!
To get my head round the numpy.i interface for SWIG, I wrote some simple
examples and documented them as much as possible. The result is here:
http://code.google.com/p/ezwidgets/wiki/NumpySWIGMinGW
I finally got round testing ARGOUTVIEW_ARRAY1 today, so it's time to ask
for some fe
13 matches
Mail list logo
