copyright: | Copyright David Abrahams 2003. See accompanying license for terms of use. |
---|
It should be possible to wrap classes which support operator() as Python methods.
http://mail.python.org/pipermail/c++-sig/2003-August/005184.html
Overload resolution currently depends on the order in which def calls are made (preferring later overloads). This should be changed so that the best-matching overload is always selected. This may await Langbinding integration, since the technology is already in Luabind.
Enabling the addition of new constructor functors or factory constructors which aren't in the underlying C++ interface. Interface still to be decided. Here is a discussion of it:
http://aspn.activestate.com/ASPN/Mail/Message/1744280However, I'm pretty sure we can't use the init<>(f) interface here because it will have to instantiate the code for the wrapped class' default constructor, which may not exist.
http://aspn.activestate.com/ASPN/Mail/Message/C++-sig/1662717
http://article.gmane.org/gmane.comp.python.c++/2044
If this gets done at all, it is going to happen in conjunction with Luabind integration.
From-Python converters should be passed an extra reference to a chain of post-call actions in the Policies object, where they can register an additional action. See the end of http://aspn.activestate.com/ASPN/Mail/Message/C++-sig/1755435
Review and possibly incorporate changes from Lijun Qin at http://aspn.activestate.com/ASPN/Mail/Message/C++-sig/1771145
Builtin correspondences between builtiin Python types and C++ types need to be documented
The structure of the framework needs to get documented; Brett Calcott has promised to turn this document into something fit for users
This project to generalizes Boost.Python to work for other languages, initially Lua. See discussions at http://lists.sourceforge.net/lists/listinfo/boost-langbinding
Consider integrating the enhancements described in http://aspn.activestate.com/ASPN/Mail/Message/C++-sig/1757092
Currently Boost.Python has several global (or function-static) objects whose existence keeps reference counts from dropping to zero until the Boost.Python shared object is unloaded. This can cause a crash because when the reference counts do go to zero, there's no interpreter. In order to make it safe to call PyFinalize() we must register an atexit routine which destroys these objects and releases all Python reference counts so that Python can clean them up while there's still an interpreter. Dirk Gerrits has promised to do this job.