Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Jim Bosch
On Tue, 2010-03-09 at 11:53 -0500, Neal Becker wrote: > No luck with boost-1.42. fedora-12 boost-1.39 seems OK. > > Lots of errors, like: > /usr/local/src/boost.hg/boost/fusion/container/vector/convert.hpp: In > instantiation of > 'boost::fusion::result_of::as_vector, > > 0>, boost::fusion::v

Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Stefan Seefeld
On 03/08/2010 07:41 PM, Neal Becker wrote: Do you intend to include some examples? That is unfortunately not quite easy, as the (in this context) interesting bits are mixed with lots of other code that is not relevant here. I will try to refactor things the way I envision this array wra

Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Neal Becker
Do you intend to include some examples? ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig

Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Neal Becker
No luck with boost-1.42. fedora-12 boost-1.39 seems OK. Lots of errors, like: /usr/local/src/boost.hg/boost/fusion/container/vector/convert.hpp: In instantiation of 'boost::fusion::result_of::as_vector, 0>, boost::fusion::vector_iterator, -0x1> > >': include/ndarray/views.hpp

Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Stefan Seefeld
On 03/09/2010 06:34 AM, Pim Schellart wrote: for fast numerical calculations callbacks into Python are not a good option. In terms of the discussion concerning compiled or header only I think that although it would be nice and clean to have a header only library, as it stands boost python has to

Re: [C++-sig] Status of Numpy support in boost python

2010-03-09 Thread Pim Schellart
Hi Everyone, wow! I am overwhelmed by the amount of response to this request. I looked at the other options and must say I agree with Jim Bosch' comment: > The whole point of using numpy with C++ is to be able to go > from raw pointers to numpy arrays and back, and that doesn't seem to be > possi