moved intro to subpage
← Revision 45 as of 2008-11-15 14:00:11
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|See ["/Introduction"] for an introduction to Boost::Python.||'''Boost.Python''' binds C++ and Python. Read [[/GettingStarted]] for an introduction.|
|Line 7:||Line 7:|
| * ["/Introduction"]
| * [[/GettingStarted]]
|Line 11:||Line 11:|
| * ["/module"] level: def,scope
| * [[/module]] level: def,scope
|Line 19:||Line 20:|
|Line 25:||Line 27:|
|1. ["/Inheritance"]||1. [[/Inheritance]]|
|Line 32:||Line 34:|
|Line 35:||Line 38:|
Boost.Python is designed with the idea in mind that users never touch a Py``Object*.
Boost.Python depends on quite a few of the other boost libraries (possibly a few others):
IIUC, ["weave"] can be used for embedding nontrivial C++ code, if you're
willing to stick it all inside one function body. Furthermore, tools like
weave.blitz() can make an enormous difference by compiling an entire C++
expression template corresponding to an arbitrarily complicated Python
expression. Surely that's nontrivial. It's definitely ''cool''. I think weave
offers enormous power to the person who's programming mostly in Python.
Boost.Python binds C++ and Python. Read /GettingStarted for an introduction.
This page serves as a forum to gather peoples' experience and as a cookbook, as it is more dynamic by nature and open to contributors.
/module level: def,scope