[C++-sig] indexing suite and py++

Hello, I want to expose following classes: class A { public: A(int a, int b) :a_(a),b_(b) {} int a_; int b_; int compute(){return a_ + b_;} }; class C : public A { public: C(int a, int b) :A(a,b){} }; struct TypeExposer // I have to ad

[C++-sig] c++-sig page out of date

I just stumbled on this, which is way out of date: http://www.python.org/community/sigs/current/cplusplus-sig/ Anybody know how to get it updated? -t ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cpl

Re: [C++-sig] Preliminary progress on Boost.Python py3k support

on Wed Apr 01 2009, Haoyu Bai wrote: > Hi, > > I did some preliminary work on BPL py3k support in these days. > > With Troy's help we have a py3k SVN tree in sandbox now, which is > branched from trunk. I also tried to compile BPL with Python 3, and by > following the error report of the compile

Re: [C++-sig] Some thoughts on py3k support

on Wed Mar 18 2009, "Niall Douglas" wrote: > On 18 Mar 2009 at 2:07, Haoyu Bai wrote: > >> According to the current behavior of Boost.Python converters, the >> wrapped function in Python 3 will return a b"Hello" (which is a bytes >> object but not a string). So code like this will broken: >> >>

Re: [C++-sig] Some thoughts on py3k support

on Thu Mar 19 2009, "Niall Douglas" wrote: > On 19 Mar 2009 at 21:53, Haoyu Bai wrote: > >> I'm felling the difference between char*, unsinged char* and the >> constant version and std::vector version of them would be a bit >> complicated and confusing. We may document it clearly, but things are

[C++-sig] method chaining in noncopyable derived class

I'm trying to wrap an API that uses method chaining (methods that return reference to same object) and restricts assignment/copy. Is there a reason I can't use return_internal_reference? # want to be able to do this in Python d = myexample.Derived("name") d.setSomething(500).execute() But I ge

Re: [C++-sig] method chaining in noncopyable derived class

Hi Brian, in this case I think the correct solution is use "return_self<>()" verify documentation in: http://www.boost.org/doc/libs/1_38_0/libs/python/doc/v2/return_arg.html#return_self-spec BR On Wed, Apr 8, 2009 at 1:06 PM, Buras, Brian wrote: > I'm trying to wrap an API that uses method chai

[C++-sig] Boost.Python help

I'm trying to build the tutorial example in the Boost.Python package (the package itself compiled and works (I think)) bjam says the test passes and gives output redirected to a file, but when I try to run the python script myself, it says it can't find module hello_ext. I have attached an exa

Re: [C++-sig] indexing suite and py++

2009/4/8 Michał Nowotka : > Hello, Good evening > I want to expose following classes: > > class A > { > public: >        A(int a, int b) >        :a_(a),b_(b) >        {} >        int a_; >        int b_; > > int compute(){return a_ + b_;} > > }; > > class C : public A > { > > public: > >        

Re: [C++-sig] c++-sig page out of date

I and David wrote the page currently shown seven years ago. A few years ago I sent a query to the Python people, about updating the page, but I never got a reply. I guess it is time to try again! My best idea for an updated page is simply this shortened version: SIG for development of Python/C+

Re: [C++-sig] PyQt (SIP) and Boost.Python interop?

Since I didn't see any other responses, I'll offer what I know, even though it doesn't directly answer your question. A few years ago I experimented with SWIG - Boost.Python integration, where you can get easy access from C++ to SWIG-wrapped objects, inside a function wrapped with Boost.Python.