Thank you Ashwin,
I has also been using Cython recently.
Thank you for the heads up :)
Dr. Lewis John McGibbney B.Sc., PhD
Engineering Applications Software Engineer Level 2
Data Management Systems and Technology Group 398J
Jet Propulsion Laboratory
California Institute of Technology
4800 Oak Grove Drive
Pasadena, California 91109-8099
Mail Stop : 158-256C
Tel: (+1) (818)-393-7402
Cell: (+1) (626)-487-3476
Fax: (+1) (818)-393-1190
Dare Mighty Things
From: Ashwin Srinath <email@example.com<mailto:firstname.lastname@example.org>>
Date: Wednesday, October 29, 2014 at 10:48 AM
To: Lewis John McGibbney
Cc: Andreas Kloeckner
Subject: Re: [PyCUDA] Advice on Switching between C, IDL and PyCUDA
I just wanted to add Cython to the list of available options to wrap C code with Python -
I've found this to work nicely in conjunction with PyCUDA.
On Wed, Oct 29, 2014 at 11:49 AM, Mcgibbney, Lewis J (398M)
It really does help. I was just not sure if it was an advised approach.
I am going to press on with a bit more confidence now and will most likely
be back here with some more cryptic context in due course.
Thank you very much for the reply.
While I'm not sure I can speak with authority on how common this type of
usage is, I think I can say with some confidence that Python is probably
one of the easier language in which to pull off a coupling such as what
you describe. In general, Python excels in the role of a 'glue' language
coupling disparate components together.
For instance, there is an existing coupling module that would let you
talk to your IDL code and seamlessly exchange data as numpy arrays:
Python is further very easy to couple with existing C code, and perhaps
the main 'problem' is that there are a large number of approaches
available that you could use, ranging from 'cffi', 'swig',
'boost.python', and many more ways of accomplishing this wrapping.
Hope that helps at least a bit,
PyCUDA mailing list