Mike,
Thanks for fixing pycxx to remove all those warnings!
I am curious: have you looked at the most recent upstream pycxx? My
impression is that there were supposedly some changes to support python
2.5, and a couple months ago I made a feeble and unsuccessful attempt to
use the updated
Mike,
I hope you don't mind my including the devel list on this; I think it is
a very important topic (although it may be one that ends up coming down
to each individual's personal experience and preferences).
The reasons pycxx worries me are:
0) C++ worries me in general--I know lots of
Eric Firing wrote:
Swig:
GvR's comments are interesting.
Do you have a pointer to those? I'd love to see them.
My thoughts on SWIG:
It's real strength is that, being automated, it can be used to wrap
large libraries, particularly ones that are constantly evolving
(wxPython). Another one
Michael Droettboom wrote:
Pyrex is fun to use and it allows code to be more gradually migrated
from Python to C. We would need to take care to not add another
run-time dependency for users.
There are no run-time dependencies with Pyrex -- it generates C code,
which is then compiled.
(As
Michael Droettboom wrote:
[...]
I think the small amount of support is a valid concern, particularly as
we move toward Py3k, if no one steps up to the plate to help with the
migration.
Do you have a sense of how difficult that migration would be?
I appreciate the way it fits so nicely
Christopher Barker wrote:
Eric Firing wrote:
Swig:
GvR's comments are interesting.
Do you have a pointer to those? I'd love to see them.
http://www.artima.com/weblogs/viewpost.jsp?thread=95863
(It was in Mike's original message.)
Eric
