Mailman 3 September 2006 - Cplusplus-sig

how to wrap multi c++ files into python by pyste?
by Qinfeng(Javen) Shi Sept. 14, 2006

Sept. 14, 2006

Dear all, I know how to wrap a single c++ file into python by pyste? Does anybody how to wrap many c++ files into several *.so? We can't wrap every single file seperately because some types and functions used in it may be delared in other file. And puting everything into a huge single file is a ugly thing. Best wishes! Javen Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

2 1

extract character from PyObject (c++)
by Markus Heller Sept. 14, 2006

Sept. 14, 2006

Dear List, I have this: a c++ PyObject which contains a unicode string. How can I isolate the individual unicode symbols from the string? Does anybody have sample code? Unfortunately I have only partly understood the definitions as given here: http://docs.python.org/api/unicodeObjects.html Thanks a lot! Markus

1 0

Help about warning C4541 in using VC7.1
by jack833 Sept. 13, 2006

Sept. 13, 2006

Here is My code . but show out warnning C4541 in VC7.1 namespace Unitest { namespace UTester { class UTester { public: UTester(){} virtual ~UTester(){} std::string Foo(){return "FOO";} }; } } warnning show: E:\ProgramFiles\Microsoft Visual Studio.NET 2003\Vc7\Boost\include\boost\python\object\inheritance.hpp(43) : warning C4541: “dynamic_cast”using option /GR- at a Polymorphism “Unitest::UTester::UTester”；May be result in unpredictable behavior. E:\ProgramFiles\Microsoft Visual Studio.NET 2003\Vc7\Boost\include\boost\python\object\inheritance.hpp(41) : while compile template class member function“boost::python::objects::dynamic_id_t boost::python::objects::polymorphic_id_generator<T>::execute(void *)” with [ T=Unitest::UTester::UTester ] can any one help me? -- View this message in context: http://www.nabble.com/Help-about-warning-C4541-in-using-VC7.1-tf2259871.htm… Sent from the Python - c++-sig forum at Nabble.com.

2 2

Re: [C++-sig] Py++ generated code ( was custom smart pointers )
by Roman Yakovenko Sept. 13, 2006

Sept. 13, 2006

On 9/12/06, David Abrahams <dave(a)boost-consulting.com> wrote: > A minimal example would have no "documentation" stringsno use of > named arguments (bp::arg(...)) and no use of things that you get by > default anyway, like default_call_policies. It would not contain > extraneous implicit conversions from int. This is a problem with many > code generators: they create an unreadable mess for anyone who wants > to understand the result. Part of the reason many people despise the > MFC Wizards. I suggest you fix Py++ so it doesn't add vacuous > "documentation" and other needless cruft. 1. Documentation was my fault. By default Py++ does not generate it. 2. default call policies is not generated anymore 3. implicit conversion - well, Py++ tries to generate as "complete code" as possible. This is done for few reasons: * educational reasons, new users to Boost.Python can learn a lot from Py++ generated code. Py++ even has gui: http://language-binding.net/pyplusplus/tutorials/pyplusplus_demo.png * to minimize size of driving script * to minimize Py++ learning curve This case is a little bit special, because a "bug" in C++. Constructors in C++ should be explicit by default. The bottom line is that I turned off generation of "implicit conversion" for constructors. In general, Py++ generates very readable code. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/

2 1

ImportError for boost.python tutorial
by Gordon Blackshields Sept. 13, 2006

Sept. 13, 2006

Hi everyone, I found this post made back in march in an attempt to get started with boost.python using mingw, after unsuccessfully trying the seemingly very simple example given in the tutorial ("hello.cpp"). After following the advice given in the link (creating the libpython24.a file and so on using pexports and dlltool and so on) but I'm still hitting a brick wall when trying to get the module imported in the interpreter. ("ImportError: dynamic module does not define init function (inithello)") I have the .dll and .pyd files made ok, but pexports shows that hello.pyd isn't exporting inithello as expected. Are there other underlying causes for this import error that i'm just not seeing? The original post that I found is below (the post was cunningly entitled "Problem") Thanks in advance, Gordon Hi, I am not sure this will solve your problem but just in case... I also had similar problems at the beginning. The problem was that the python library shipped with Python installation only works with Microsoft compatible link and I was using, as you do, mingw (gcc). In http://www.boost.org/libs/python/doc/building.html#mingw you will find a detail explanation of what happens and how to solve it. It's really simple. Hope this will help... It is really frustrating at the beginning but once it starts working... boost::python is wonderful! Best Regards, Pedro. > Hi, > I'm trying to build the basic boost.python tutorial that comes with the > distribution. I'm using bjam and mingw. It builds the module, but > upon import, it gives this error: > > ImportError: dynamic module does not define init function (inithello) > > I've found other threads with this problem as a topic, but no > solutions. Somebody has to have solved this.... > > Any ideas? > > Thanks, > -Justin > > OH yeah, I'm using Active Python (perhaps that's it?) -- Pedro -- _______________________________________________ For the largest FREE email in Ireland (25MB) and 20MB of online file storage space - Visit http://www.campus.ie

2 1

New Patch for opaque_pointer_converter
by Gottfried Ganßauge Sept. 12, 2006

Sept. 12, 2006

Please find attached a completely new patch against the current CVS Head. This incorporates my patch from earlier today into the CVS Head. Further I implemented cross module support in so far as the converter registers itself only if not another module already has registered the same converter before. The opaque test case has been update to check for the segmentation fault mentioned in my previous post. A test case for the cross module support is included (crossmod_opaque). I also updated the documentation for opaque. I tested my patch with - GCC-4.1 running on GNU/Linux 2.6.16.21-0.13-default x86_64 - Visual-C++-6.5 running on Windows XP - Visual-C++-7.1 running on Windows XP The patch is applied by calling patch -p1 < opaque_patch in the root of the boost hierarchy. Files patched are: boost_head/boost/python/opaque_pointer_converter.hpp boost_head/libs/python/doc/v2/opaque.html boost_head/libs/python/doc/v2/opaque_pointer_converter.html boost_head/libs/python/doc/v2/reference.html boost_head/libs/python/doc/v2/return_opaque_pointer.html boost_head.orig/libs/python/test/crossmod_opaque_a.cpp boost_head/libs/python/test/crossmod_opaque_a.cpp boost_head/libs/python/test/crossmod_opaque_b.cpp boost_head/libs/python/test/crossmod_opaque.py boost_head/libs/python/test/Jamfile boost_head/libs/python/test/Jamfile.v2 boost_head/libs/python/test/opaque.py Enjoy ... Gottfried diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/boost/python/opaque_pointer_converter.hpp boost_head/boost/python/opaque_pointer_converter.hpp --- boost_head.orig/boost/python/opaque_pointer_converter.hpp 2006-02-12 17:09:08.000000000 +0100 +++ boost_head/boost/python/opaque_pointer_converter.hpp 2006-09-09 01:29:10.942429483 +0200 @@ -1,4 +1,4 @@ -// Copyright Gottfried Ganßauge 2003. +// Copyright Gottfried Ganßauge 2003..2006. // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) @@ -11,6 +11,7 @@ # include <boost/python/detail/prefix.hpp> # include <boost/python/lvalue_from_pytype.hpp> # include <boost/python/to_python_converter.hpp> +# include <boost/python/converter/registrations.hpp> # include <boost/python/detail/dealloc.hpp> # include <boost/python/detail/none.hpp> # include <boost/python/type_id.hpp> @@ -44,9 +45,16 @@ { opaque() { - type_object.tp_name = const_cast<char*>(type_id<Pointee*>().name()); - converter::registry::insert(&extract, type_id<Pointee>()); - converter::registry::insert(&wrap, type_id<Pointee*>()); + if (type_object.tp_name == 0) + { + type_object.tp_name = const_cast<char*>(type_id<Pointee*>().name()); + if (PyType_Ready (&type_object) < 0) + { + throw error_already_set(); + } + + register_self(); + } } static opaque instance; @@ -78,6 +86,17 @@ } } + void register_self() { + converter::registration const *existing = + converter::registry::query (type_id<Pointee*>()); + + if ((existing == 0) || (existing->m_to_python == 0)) + { + converter::registry::insert(&extract, type_id<Pointee>()); + converter::registry::insert(&wrap, type_id<Pointee*>()); + } + } + struct python_instance { PyObject_HEAD diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/doc/v2/opaque.html boost_head/libs/python/doc/v2/opaque.html --- boost_head.orig/libs/python/doc/v2/opaque.html 1970-01-01 01:00:00.000000000 +0100 +++ boost_head/libs/python/doc/v2/opaque.html 2006-09-09 01:15:56.899776733 +0200 @@ -0,0 +1,134 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + +<html> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <link rel="stylesheet" type="text/css" href="../boost.css"> + + <title>Boost.Python - <boost/python/opaque_pointer_converter.hpp></title> + </head> + + <body> + <table border="0" cellpadding="7" cellspacing="0" width="100%" summary= + "header"> + <tr> + <td valign="top" width="300"> + <h3><a href="../../../../index.htm"><img height="86" width="277" + alt="C++ Boost" src="../../../../boost.png" border="0"></a></h3> + </td> + + <td valign="top"> + <h1 align="center"><a href="../index.html">Boost.Python</a></h1> + + <h2 align="center">Header + <boost/python/opaque_pointer_converter.hpp></h2> + </td> + </tr> + </table> + <hr> + + <h2>Contents</h2> + + <dl class="page-index"> + <dt><a href="#classes">Classes</a></dt> + + <dd> + <dl class="page-index"> + <dt><a href="#opaque-spec">Class template + <code>opaque<Pointee></code></a></dt> + + <dd> + <dl class="page-index"> + <dt><a href="#opaque-spec-synopsis">Class template + <code>opaque</code> synopsis</a></dt> + </dl> + </dd> + </dl> + </dd> + + <dt><a href="#macros">Macros</a></dt> + <dd> + <dl class="page-index"> + <dt><a href="#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec">Macro + <code>BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID</code></a></dt> + </dl> + </dd> + + <dt><a href="#see-also">See Also</a></dt> + </dl> + <hr> + + <h2><a name="classes"></a>Classes</h2> + + <h3><a name="opaque-spec"></a>Class template + <code>opaque<P></code></h3> + + <p><code>opaque<></code> registers itself as a converter from + Python objects to pointers to undefined types and vice versa.</p> + + <h4><a name="opaque-spec-synopsis"></a>Class template + <code>opaque</code> synopsis</h4> +<pre> +namespace boost { namespace python +{ + template<class Pointee> + struct opaque + { + opaque(); + }; +}} +</pre> + + <h4><a name="opaque-spec-constructor"></a>Class template + <code>opaque</code> constructor</h4> +<pre> +opaque(); +</pre> + + <dl class="function-semantics"> + <dt><b>Effects:</b> + <ul> + <li>Registers the instance as a + <a href="lvalue_from_pytype.html#lvalue_from_pytype-spec"> <code>lvalue_from_pytype</code></a> + converter from Python objects into opaque pointers.</p> + <p>The Python Objects created are named after the type pointed to + by the opaque pointer being wrapped.</p></li> + <li>Registers the instance as a + <a href="to_python_converter.html#to_python_converter-spec"> <code>to_python_converter</code></a> + from opaque pointers to Python objects.</p></li> + </ul> + <p>If there is already an instance registered by another module, this + instance doesn't try to register again in order to avoid warnings + about multiple registrations.</p> + + <h4>Note</h4> + <p>Normally only a single instance of this class is created for every + Pointee.</p> + </dt> + </dl> + + <h2><a name="macros"></a>Macros</h2> + + <h3><a name="BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"></a> + Macro BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(Pointee)</h3> + <p>This macro must be used to define specializations of the + <a href="type_id.html#type_id-spec">type_id</a> function + which can't be instantiated for incomplete types.</p> + <h4>Note</h4> + <p>The macro must be invoked in every translation unit which uses the + opaque converter.</p> + + <h2><a name="see-also"></a>See Also</h2> + <p> + <a href="return_opaque_pointer.html">return_opaque_pointer</a> + </p> + + <p>Revised + 10 September, 2006 + </p> + + <p><i>© Copyright 2003..2006 Haufe Mediengruppe. All Rights + Reserved.</i></p> + </body> +</html> + diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/doc/v2/opaque_pointer_converter.html boost_head/libs/python/doc/v2/opaque_pointer_converter.html --- boost_head.orig/libs/python/doc/v2/opaque_pointer_converter.html 2005-08-03 14:20:42.000000000 +0200 +++ boost_head/libs/python/doc/v2/opaque_pointer_converter.html 1970-01-01 01:00:00.000000000 +0100 @@ -1,142 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> - -<html> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <link rel="stylesheet" type="text/css" href="../boost.css"> - - <title>Boost.Python - <boost/python/opaque_pointer_converter.hpp></title> - </head> - - <body> - <table border="0" cellpadding="7" cellspacing="0" width="100%" summary= - "header"> - <tr> - <td valign="top" width="300"> - <h3><a href="../../../../index.htm"><img height="86" width="277" - alt="C++ Boost" src="../../../../boost.png" border="0"></a></h3> - </td> - - <td valign="top"> - <h1 align="center"><a href="../index.html">Boost.Python</a></h1> - - <h2 align="center">Header - <boost/python/opaque_pointer_converter.hpp></h2> - </td> - </tr> - </table> - <hr> - - <h2>Contents</h2> - - <dl class="page-index"> - <dt><a href="#classes">Classes</a></dt> - - <dd> - <dl class="page-index"> - <dt><a href="#opaque_pointer_converter-spec">Class template - <code>opaque_pointer_converter<P></code></a></dt> - - <dd> - <dl class="page-index"> - <dt><a href="#opaque_pointer_converter-spec-synopsis">Class template - <code>opaque_pointer_converter</code> synopsis</a></dt> - </dl> - </dd> - </dl> - </dd> - - <dt><a href="#macros">Macros</a></dt> - <dd> - <dl class="page-index"> - <dt><a href="#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec">Macro - <code>BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID</code></a></dt> - </dl> - </dd> - - <dt><a href="#examples">Example</a></dt> - - <dt><a href="#see-also">See Also</a></dt> - </dl> - <hr> - - <h2><a name="classes"></a>Classes</h2> - - <h3><a name="opaque_pointer_converter-spec"></a>Class template - <code>opaque_pointer_converter<P></code></h3> - - <p><code>opaque_pointer_converter<></code> is derived from - <a href="to_python_converter.html#to_python_converter-spec"> - <code>to_python_converter</code></a> - and registers itself as an - <a href="lvalue_from_pytype.html#lvalue_from_pytype-spec"> - <code>lvalue_from_pytype</code></a> converter from Python objects - into pointers to undefined types. - Thus it may be used as a converter from opaque pointers into - Python objects and vice versa.</p> - - <h4><a name="opaque_pointer_converter-spec-synopsis"></a>Class template - <code>opaque_pointer_converter</code> synopsis</h4> -<pre> -namespace boost { namespace python -{ - template<class Pointer> - struct opaque_pointer_converter - : to_python_converter< - Pointer, opaque_pointer_converter<Pointer> > - { - explicit opaque_pointer_converter(char const* name); - }; -}} -</pre> - - <h4><a name="opaque_pointer_converter-spec-constructor"></a>Class template - <code>opaque_pointer_converter</code> constructor</h4> -<pre> -explicit opaque_pointer_converter(char const* name); -</pre> - - <dl class="function-semantics"> - <dt><b>Effects:</b> - <p>Registers the instance as a - <a href="lvalue_from_pytype.html#lvalue_from_pytype-spec"> - <code>lvalue_from_pytype</code></a> converter from Python objects - into opaque pointers.</p> - <p>The name is used for the type of the Python Objects created; - it should be printable but needn't be an - <a href="definitions.html#ntbs">ntbs</a> because the object type is - not supposed to be user constructible within python scripts.</p> - </dt> - </dl> - - <h2><a name="macros"></a>Macros</h2> - - <h3><a name="BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"></a> - Macro BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(Pointee)</h3> - <p>This macro must be used to define specializations of the - <a href="type_id.html#type_id-spec">type_id</a> function - which can't be instantiated for incomplete types.</p> - <h4>Note</h4> - <p>In order for this to work in a cross-module environment the macro must - be invoked in every translation unit which uses the - opaque_pointer_converter.</p> - - <h2><a name="examples"></a>Example</h2> - - please see example for <a href="return_opaque_pointer.html#examples"> - return_opaque_pointer</a>. - - <h2><a name="see-also"></a>See Also</h2> - <p> - <a href="return_opaque_pointer.html">return_opaque_pointer</a> - </p> - - <p>Revised - 10 March, 2003 - </p> - - <p><i>© Copyright 2003 Haufe Mediengruppe. All Rights - Reserved.</i></p> - </body> -</html> - diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/doc/v2/reference.html boost_head/libs/python/doc/v2/reference.html --- boost_head.orig/libs/python/doc/v2/reference.html 2006-01-16 21:37:23.000000000 +0100 +++ boost_head/libs/python/doc/v2/reference.html 2006-09-09 01:15:09.923641734 +0200 @@ -904,26 +904,26 @@ </dd> <dt><a href= - "opaque_pointer_converter.html">opaque_pointer_converter.hpp</a></dt> + "opaque.html">opaque_pointer_converter.hpp</a></dt> <dd> <dl class="index"> <dt><a href= - "opaque_pointer_converter.html#classes">Classes</a></dt> + "opaque.html#classes">Classes</a></dt> <dd> <dl class="index"> <dt><a href= - "opaque_pointer_converter.html#opaque_pointer_converter-spec">opaque_pointer_converter</a></dt> + "opaque.html#opaque-spec">opaque</a></dt> </dl> </dd> - <dt><a href="opaque_pointer_converter.html#macros">Macros</a></dt> + <dt><a href="opaque.html#macros">Macros</a></dt> <dd> <dl class="index"> <dt><a href= - "opaque_pointer_converter.html#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"> + "opaque.html#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"> BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID</a></dt> </dl> </dd> diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/doc/v2/return_opaque_pointer.html boost_head/libs/python/doc/v2/return_opaque_pointer.html --- boost_head.orig/libs/python/doc/v2/return_opaque_pointer.html 2004-10-05 17:45:46.000000000 +0200 +++ boost_head/libs/python/doc/v2/return_opaque_pointer.html 2006-09-09 01:17:07.269985049 +0200 @@ -67,7 +67,7 @@ undefined types such that the return value is copied into a new Python object.</p> <p>In addition to specifying the <code>return_opaque_pointer</code> - policy the <a href="opaque_pointer_converter.html#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"> + policy the <a href="opaque.html#BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID-spec"> <code>BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID</code></a> macro must be used to define specializations for the <a href="type_id.html#type_id-spec">type_id</a> function @@ -174,8 +174,8 @@ <h2><a name="see-also"></a>See Also</h2> <p> - <a href="opaque_pointer_converter.html"> - opaque_pointer_converter</a> + <a href="opaque.html"> + opaque</a> </p> <p>Revised diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/crossmod_opaque_a.cpp boost_head/libs/python/test/crossmod_opaque_a.cpp --- boost_head.orig/libs/python/test/crossmod_opaque_a.cpp 1970-01-01 01:00:00.000000000 +0100 +++ boost_head/libs/python/test/crossmod_opaque_a.cpp 2006-09-09 01:27:49.269150496 +0200 @@ -0,0 +1,26 @@ +// Copyright Gottfried Ganßauge 2006. +// Distributed under the Boost Software License, Version 1.0. (See +// accompanying file LICENSE_1_0.txt or copy at +// http://www.boost.org/LICENSE_1_0.txt) +# include <boost/python/return_opaque_pointer.hpp> +# include <boost/python/def.hpp> +# include <boost/python/module.hpp> +# include <boost/python/return_value_policy.hpp> + +typedef struct opaque_ *opaque; + +opaque the_op = ((opaque) 0x47110815); + +opaque get() { return the_op; } + +BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(opaque_) + +namespace bpl = boost::python; + +BOOST_PYTHON_MODULE(crossmod_opaque_a) +{ + bpl::def ( + "get", + &::get, + bpl::return_value_policy<bpl::return_opaque_pointer>()); +} diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/crossmod_opaque_b.cpp boost_head/libs/python/test/crossmod_opaque_b.cpp --- boost_head.orig/libs/python/test/crossmod_opaque_b.cpp 1970-01-01 01:00:00.000000000 +0100 +++ boost_head/libs/python/test/crossmod_opaque_b.cpp 2006-09-09 01:27:59.984268728 +0200 @@ -0,0 +1,26 @@ +// Copyright Gottfried Ganßauge 2006. +// Distributed under the Boost Software License, Version 1.0. (See +// accompanying file LICENSE_1_0.txt or copy at +// http://www.boost.org/LICENSE_1_0.txt) +# include <boost/python/return_opaque_pointer.hpp> +# include <boost/python/def.hpp> +# include <boost/python/module.hpp> +# include <boost/python/return_value_policy.hpp> + +typedef struct opaque_ *opaque; + +opaque the_op = ((opaque) 0x47110815); + +opaque get() { return the_op; } + +BOOST_PYTHON_OPAQUE_SPECIALIZED_TYPE_ID(opaque_) + +namespace bpl = boost::python; + +BOOST_PYTHON_MODULE(crossmod_opaque_b) +{ + bpl::def ( + "get", + &::get, + bpl::return_value_policy<bpl::return_opaque_pointer>()); +} diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/crossmod_opaque.py boost_head/libs/python/test/crossmod_opaque.py --- boost_head.orig/libs/python/test/crossmod_opaque.py 1970-01-01 01:00:00.000000000 +0100 +++ boost_head/libs/python/test/crossmod_opaque.py 2006-09-09 01:28:09.835458056 +0200 @@ -0,0 +1,14 @@ +# Copyright Gottfried Ganßauge 2006. +# Distributed under the Boost Software License, Version 1.0. (See +# accompanying file LICENSE_1_0.txt or copy at +# http://www.boost.org/LICENSE_1_0.txt) + +print "running..." + +import crossmod_opaque_a +import crossmod_opaque_b + +crossmod_opaque_a.get() +crossmod_opaque_b.get() + +print "Done." diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/Jamfile boost_head/libs/python/test/Jamfile --- boost_head.orig/libs/python/test/Jamfile 2006-03-03 10:08:39.000000000 +0100 +++ boost_head/libs/python/test/Jamfile 2006-09-09 00:24:06.515671506 +0200 @@ -170,6 +170,10 @@ [ bpl-test extract ] +[ +bpl-test crossmod_opaque + : crossmod_opaque.py crossmod_opaque_a.cpp crossmod_opaque_b.cpp +] [ bpl-test opaque ] [ bpl-test voidptr ] diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/Jamfile.v2 boost_head/libs/python/test/Jamfile.v2 --- boost_head.orig/libs/python/test/Jamfile.v2 2006-08-24 21:03:35.000000000 +0200 +++ boost_head/libs/python/test/Jamfile.v2 2006-09-09 00:23:20.919424482 +0200 @@ -114,6 +114,10 @@ [ bpl-test extract ] +[ +bpl-test crossmod_opaque + : crossmod_opaque.py crossmod_opaque_a.cpp crossmod_opaque_b.cpp +] [ bpl-test opaque ] [ bpl-test voidptr ] diff -r -x 'Entries*' -x .jamdeps -x '*.test' -x '*.run' -x '*.output' -x '*.o' -x '*.so' -uN boost_head.orig/libs/python/test/opaque.py boost_head/libs/python/test/opaque.py --- boost_head.orig/libs/python/test/opaque.py 2003-08-26 15:11:51.000000000 +0200 +++ boost_head/libs/python/test/opaque.py 2006-09-09 01:27:25.419113167 +0200 @@ -1,5 +1,5 @@ # -*- coding: iso-latin-1 -*- -# Copyright Gottfried Ganßauge 2003. Permission to copy, use, +# Copyright Gottfried Ganßauge 2003..2006. Permission to copy, use, # modify, sell and distribute this software is granted provided this # copyright notice appears in all copies. This software is provided # "as is" without express or implied warranty, and with no claim as @@ -66,6 +66,11 @@ >>> try: use2(get()) ... except TypeError: pass ... else: print 'expected a TypeError' + + This used to result in a segmentation violation + +>>> type(get()) != type (get2()) +1 """ def run(args = None): import sys

3 5

PyCode_New and new.code() functions
by anders langlands Sept. 12, 2006

Sept. 12, 2006

Does anyone know how to use either PyCode_New or new.code()?? Specifically I want to use new.code() and new.function() to generate some python functions from strings, which I can then call in python at some later time. My trouble is I can find exactly zero documentation on the use of these functions :( Any help would be greatly appreciated. Cheers, Anders

2 7

[tutorial] Auto-Overloading example bug?
by Roman Yakovenko Sept. 12, 2006

Sept. 12, 2006

Hi. I could be wrong, but it seems to me that the Boost.Python tutorials contains bug. ( http://boost.org/libs/python/doc/tutorial/doc/html/python/functions.html#py…) The compiler ( I use msvc 7.1 ) is not able to compile the code. The main reason is that it can not decide what "f" to select. I mean, it does not know what address it should pass to "def" function. The same thing occurs for BOOST_PYTHON_MEMBER_FUNCTION_OVERLOADS. It seems to me that it is right. Some thoughts. I think, that in this case( auto-overloading example ) function "def" should not take reference to function. It should be enough to pass an instance of the constructed class. Same logic could be applied on class_::def method too. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/

3 7

Is there a way to automatically convert a smart_ptr to a held_type (try 2)
by Allen Bierbaum Sept. 12, 2006

Sept. 12, 2006

Note: I posted this message a very long time ago on this list and still haven't found a solution. Several months ago David suggested that I repost the message again to see if anyone can help out. I am finally getting back to this project so here is the repost. I am wrapping a C++ library with boost.python that has multiple types of smart ptrs for it's objects. It has a ptr<> type that holds the object and provides a ref counting interface (through and addRef()/subRef() interface). It then has a ref_ptr<> type that acts like a "standard" smart pointer by holding a ptr<> internally and calling the ref handling operations upon construction and destruction. To correctly handle the memory for the objects, I want my boost.python class wrappers for a class T to be held using ref_ptr<T>. I can do this with: class_<T, bases<...>, ref_ptr<T> >("T",...); This all works fine. I run into a problem though when I want to use wrapped method that return ptr<>'s to objects instead of a full ref_ptr<>. For example if I wrap a method like this: ptr<Base> createObject() { ... } then when I call this from boost.python it needs to figure out that it should convert the ptr<Base> to a ref_ptr<Base>. I know that I can use register_ptr_to_python<ptr<Base> > to register a to_python converter for the type, but as I understand it this will cause the python wrapper to store the C++ object using a ptr<> type internally. This won't work correctly because it will not do any memory reference counting. What I need is a way to tell boost python that anytime it needs to convert a ptr<Base> to python it should first convert it to a ref_ptr<Base> (using a standard copy constructor in ref_ptr<>) and then use this ref_ptr as the held type like normal. At first I thought that implicitly_convertible<> would help: implicitly_convertible<ptr<Base>, ref_ptr<Base> >(); But this doesn't seem to do anything for me. (this really isn't too surprising since this isn't what implicitly_convertible is for, but it seemed worth a try). Has anyone else ran into anything similar? Any ideas? Thanks, Allen

3 25

RuntimeError: unidentifiable C++ exception
by Qun Cao Sept. 12, 2006

Sept. 12, 2006

Hi Everyone, I created a simple class wrapper like this BOOST_PYTHON_MODULE(PythonTest) { class_<MyClass,boost::noncopyable>("pMyClass", init<char const*>()); } When I try to initialize pMyClass in python, I got this error: Traceback (most recent call last): File "<stdin>", line 1, in ? RuntimeError: unidentifiable C++ exception MyClass is part of a third party GameEngine, I can successfully use it in C++. Can anyone suggest what might went wrong here? Thanks a lot, Qun

3 2

[Py++] First imressions
by Kirill Lapshin Sept. 12, 2006

Sept. 12, 2006

Hello, Recently I was charged with exposing our project to Python, and naturally went to Boost.Python documentation. After digging a bit, learning, etc, I decided to give some code generator a try -- so the choice was Pyste or Py++. I've decided to try the latter one first, since it seems to have quite powerful query language, and was offering a promise of doing certain operations in bulk. Another reason was that Py++ is actively maintained. Long story short, I dived in, and I haven't look back. I am quite happy with progress, albeit the initial development is not finished yet, so it is not a success story yet, but I am quite confident it will become one quite soon. I would like to thank Roman for his hard work on Py++ and for being extremely helpful in our private e-mail discussion. Just for the record I would like to post some of the problems I had and the way they were resolved. 1. The way overrides are generated does not compile on MSVC8 (2005). Looks like the problem is in conversion of return type if return type is bool or enum. For example virtual bool is_representative( ) const { bp::override func_is_representative = this->get_override( "is_representative" ); return func_is_representative( ); // errors out } error C2440: 'return' : cannot convert from 'boost::python::detail::method_result' to 'bool' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called Don't know why is this happening, but the good news, there is a workaround. One can use explicit conversion of return type, i.e. return func_is_representative()..as(&boost::type<T>()); If someone could verify this problem, I guess the solution would be to patch code creator. 2. How to disable function overriding. I don't really need ability to override virtual functions from Python anyway, and moreover using wrapper classes does not seem to work for me, since I am trying to expose abstract interfaces to python and hide concrete implementations (hence wrapper is abstract as well and can't be instantiated). Maybe there is still a way to expose it with wrapper, but I've decided not bother for now. Roman suggested following way to suppress overriding: from pygccxml import declarations members = cls.decls( declarations.virtuality_type_matcher( declarations.VIRTUALITY_TYPES.VIRTUAL ) , decl_type=pd.member_calldef_t , allow_empty=True) members.set_virtuality( declarations.VIRTUALITY_TYPES.NOT_VIRTUAL ) Note that Py++ differentiates between VIRTUAL and PURE_VIRTUAL, so above listed code does not cover pure virtual functions. 3. Observation: Py++ generates wrappers even if there is no virtual functions, but there is nested class/struct. Nested enums are Ok. 4. Gccxml is buggy, especially with respect to default arguments. See http://language-binding.net/pygccxml/design.html#patchers. In my case I had problems with default std::vector<T> arguments. Those can be worked around manually with mb = module_builder_t( ... ) Foo = mb.class_( 'Foo' ) Foo_constructor = Foo.constructor( select write constructor ) #help: http://language-binding.net/pygccxml/query_interface.html Foo_constructor.arguments[0].default_value = fixed default value 5. Precompiled header support is not implemented even though documentation claims it is. Roman says it is in works. For a meantime one can use following workaround: mb.code_creator.adopt_creator( code_creators.include_t(header='_pch.hpp'), 0) md.split_module(...) 6. shared_ptr<T> works out of the box, while shared_ptr<const T> does not. Roman gave me following pointers: http://boost.org/libs/python/doc/v2/register_ptr_to_python.html Also read this: http://language-binding.net/pygccxml/apidocs/pygccxml.declarations.type_tra… Now you can implement some general solution similar to http://python-ogre.python-hosting.com/file/trunk/python-ogre/shared_ptr.py I did not have time to try it yet, but planning to do it soon. Cheers, Kirill

2 1

Possible to inspect type of a boost::python::object
by anders langlands Sept. 12, 2006

Sept. 12, 2006

Currently I'm using extract<T>::check() over a bunch of different types to decide what to do with python objects. Is there any way to inspect the type directly? A

2 1

Patch for py++
by Ganssauge, Gottfried Sept. 11, 2006

Sept. 11, 2006

I had to make the following patch to pyplusplus\code_repository\array_1.py in order to make it compile using Visual-C++ 6.5: Index: array_1.py =================================================================== --- array_1.py (Revision 494) +++ array_1.py (Arbeitskopie) @@ -28,13 +28,14 @@ inline void raise_on_out_of_range( long unsigned int size, long unsigned int index ){ - if( index < 0 || size <= index ){ + if( size <= index ){ throw std::out_of_range("index out of range"); } } template< class TItemType, long unsigned int size > struct const_array_1_t{ + typedef boost::call_traits<const TItemType>::param_type ref; const_array_1_t( TItemType const * const data ) : m_data( data ){ @@ -47,8 +48,7 @@ return size; } - typename boost::call_traits<const TItemType>::param_type - item_ref( long unsigned int index ) const{ + ref item_ref( long unsigned int index ) const{ raise_on_out_of_range( size, index ); return m_data[index]; } @@ -61,6 +61,7 @@ template< class TItemType, long unsigned int size > struct array_1_t{ + typedef boost::call_traits<const TItemType>::param_type ref; array_1_t( TItemType * data ) : m_data( data ){ @@ -73,15 +74,14 @@ return size; } - typename boost::call_traits<const TItemType>::param_type - item_ref( long unsigned int index ) const{ + ref item_ref( long unsigned int index ) const{ raise_on_out_of_range( size, index ); return m_data[index]; } void set_item( long unsigned int index - , typename boost::call_traits<const TItemType>::param_type new_value ){ + , ref new_value ){ raise_on_out_of_range( size, index ); m_data[index] = new_value; } Cheers, Gottfried

2 2

Re: [C++-sig] array of strings in boost python
by David Abrahams Sept. 11, 2006

Sept. 11, 2006

The following message is a courtesy copy of an article that has been posted to gmane.comp.lib.boost.user as well. <ctrembla(a)pcigeomatics.com> writes: > Hi, > > newbie in python and boost::python Please post Boost.Python questions to the C++-sig: http://www.boost.org/more/mailing_lists.htm#cplussig > I have a method in c++ that returns a vector of strings, how can i > expose this method in python, and how should i use it in python Sorry to turn the question around on you, but how do you /want/ to be able to use it in Python? That will determine how you should expose it. You might look into http://boost.org/libs/python/doc/v2/indexing.html#vector_indexing_suite_cla… to see if it meets your needs. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Bug in opaque_pointer_converter and patch
by Ganssauge, Gottfried Sept. 8, 2006

Sept. 8, 2006

While debugging a python extension I found out that a segmentation fault was produced by the python statement print type(some_opaque_pointer) After some further debugging I found out that all instances created from opaque_pointer_converter had a type object which itself didn't have a type, and this finally lead to the crash. Find attached a patch which corrects this behaviour by initialising the type object using PyType_Ready(). Cheers, Gottfried

1 0

[boost.python] Indexing suite problems with convertable element type
by Kirill Lapshin Sept. 7, 2006

Sept. 7, 2006

Hi, I am just making my first step in boost.python world, so please forgive me for potential FAQ, but I can't find an answer in docs and by googling. I have a custom date class, that I registered for conversion to Python's datetime.date object. Individual dates convert fine, but when I registered vector<date> with indexing suite, I have a problem that I can insert python date objects into vector, but can't extract them. E.g. >>> v = vector_day() >>> v.append( datetime.date(2006,1,1) ) >>> len(v) 1 >>> v[0] Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: No Python class registered for C++ class class day vector_day is exposed like this: bp::class_< std::vector<day, std::allocator<day> > >( "vector_day" ) .def( bp::vector_indexing_suite< ::std::vector<day, std::allocator<day> > >() ); As I said, individual date objects convert just fine back and forth, i.e. function day test_day( day x ) { return x+1; } exposed as typedef day ( *function_ptr_t )( day ); bp::def( "test_day", function_ptr_t( &test_day ), ( bp::arg("x") ), bp::default_call_policies() ); can be used from Python without problems: >>> test_day( datetime.date(2006,1,1) ) datetime.date(2006, 1, 2) What am I doing wrong? Regards, Kirill Lapshin

2 2

[Py++] Nested enum as default arg
by Kirill Lapshin Sept. 7, 2006

Sept. 7, 2006

Hi, Suppose I have struct Foo { enum Bar {BAR1, BAR2}; explicit Foo(Bar arg = BAR1); }; Py++ generates code that tries to add constructor (and default argument) prior to enum being registered. Result is exception in module import. Any ideas how to fix / work around? Other then moving enum outside the class? Cheers, Kirill

2 7

boost::python tutorial on overloading not up-to-date?
by Neal Becker Sept. 7, 2006

Sept. 7, 2006

In boost::python tutorial there is a whole section on manual overloading. AFAICT, overloading "just works" without my doing anything. Is this information out-of-date?

1 0

Re: [C++-sig] Py++ wrapper generation and docstrings
by Ganssauge, Gottfried Sept. 4, 2006

Sept. 4, 2006

> -----Original Message----- > From: Roman Yakovenko [mailto:roman.yakovenko@gmail.com] > Sent: Sunday, September 03, 2006 2:49 PM > To: Ganssauge, Gottfried > Subject: Re: Py++ wrapper generation and docstrings > > On 9/3/06, Ganssauge, Gottfried <Gottfried.Ganssauge(a)haufe.de> wrote: > > Hi Roman, > > > > I'm still working on my API with Py++ and there are a few bits left: > > Is this because of Py++ or you have pretty big project :-)? Neither nor I guess. The project is quite old, it's got a C-API and the API is highly irregular :-( > > > 1.) my API contains several functions expecting pointers to callback > > functions. > > Those callbacks get an instance pointer as one of their > arguments > > which has to be supplied as well. > > An example: > > typedef int (*callback_t) (void *instance); > > > > int search (void *instance, callback_t callback); > > > > I have written a generator which generates a wrapper like this: > > > > int wrap_callback_t (void *instance) { > > You can use boost::python::object No I can't :-( Gccxml botches on the bpl headers: $ cat x.hpp # include <boost/python.hpp> boost::python::object test (); $ gccxml -I ../../../../../../FremdProdukte/boost2 -I /usr/include/python2.4 x.hpp -fxml=test.xml ../../../../../../FremdProdukte/boost2/boost/python/object_core.hpp:285: sorry, unimplemented: call_expr cannot be mangled due to a defect in the C++ ABI This problem has been reported on the gccxml list already ... > > > try { > > return (boost::python::call<int> > > (reinterpret_cast<PyObject *> (instance))); > > } > > > > catch (...) { > > return (-1); // python > exceptions must not > > disrupt program flow > > } > > } > > > > int search_wrapper (PyObject *p) { > > return (search (p, &wrap_callback_t)); > > } > > > > This works quite well, but ... > > How do I make this generator interact with generators already > > supplied by Py++ > > For example: > > you're planning to support automatic conversion of > pointers to > > C++ array arguments from python sequences > > May be the next article will provide you with the answer. > https://realityforge.vrsource.org/view/PyppApi/CodeInserter > > I and Matthias work on this feature this days. Comments and test cases > are welcome :-) I'll have a look at it. > > > Now suppose the following: > > type char array_t [7]; > > > > int search2 (void *instance, callback_t cb, > array_t *result); > > If you already create a wrapper, you can create "better" wrapper: > > boost::python::tuple search2( void* instance, callback_t cb ){ > ... > return boost::python::make_tuple( .... ) > } That's what I'd like to achieve - but automatically! > > > How would both our generators interact with each other? > > I don't see the whole picture, so I can not answer your question. > I assume that you have some functions that take pointer to > callback, right? > You can not expose these functions as is, so you have to > write a wrapper for > them. Basically you should exclude the function from being exported, > and then you > should add your declaration and registration code. Next link should > help you with > your task: > > http://www.language-binding.net/pyplusplus/documentation/inserting_code. html > > > > Finally I'm not sure about when to run my generator. > > In your case you may consider to run it twice: > > 1. first time you can generate your own header file. This file will > contain all wrappers. > 2. second time you weel feed just generated header fileand original > sources to Py++. > > > Currently I'm running it on every declaration > expecting callback- > > and instance pointers. > > The declarations are then modified like this (f is a > declaration > > for "search"): > > pyobject_type = pointer_t (dummy_type_t ("PyObject"))): > > wrapperargs = [ argument_t (name = "instance", type = > > pyobject_type) ] > > function = f.name > > f.name = "%s_wrapper" % function > > f.arguments = wrapperargs > > f.exportable = None # redo the check for exportability > > # rename f if this is the first wrapper > > if not f.alias or f.name == f.alias: > > f.rename (function) > > > > Does this look reasonable? (at least it works :-0) > > No. Too much work and too much details. Consider the way I described. That was my first attempt, but it became difficult to chain several generators together. Eventually I should really consider doing several generator passes to a temp file until the temp file doesn't change anymore. This could take quite some time because gccxml must parse the intermediate files... Furthermore I'm not yet sure how to forward the original function names ... > > > I got another generator which generates wrappers for functions > > expecting "const unsigned char *" arguments for strings ... > > > > 2.) docstring extraction is not really usable at the moment > > consider the attached test case > > [test1.hpp, pypp_test1.py] > > > > When using the "latin1_doc_string" doc_extractor some unicode > > exception is thrown. > > I will take a look on this. I did not thought about unicodes :-(. It > will take some time to > convert Py++ to support it. I think, that doc_extractor will change, > because you will > have to provide encoding. Otherwise, I will not be able to > write code to files. This could be a property on the doc_extractor. > Also quick work around exists: > > my_module > class_< X >( "X" ) > .def( "do_smth", ... ) > ; > > import my_module > my_module.X.__doc__ = .... > my_module.X.do_smth.__doc__ = ... > > This will work and it is simple to generate it. Ok. > > > When using the "ascii_doc_string" doc_extractor invalid code is > > generated > > Only when the doc extractor returns a string which is > conforming to > > C++ syntax everything runs smooth. > > This is how it was created. See explanation later. > > > Pragmatically I would request that doc extractors must return > > docstrings conforming to C++ syntax. > > This means you wouldn't need to change Py++ - just the > > documentation. > > You could supply some function which makes C++-syntax > from a normal > > string like > > def make_cstring (s): > > return ('"%s"' % (repr (s) [1:-1])) > > It is not as simple as you think :-). You have to escape " in the > string and you have to do > it in a smart way. That is why I leaved this to user. If you want we > can work together > to improve the situation. I will make Py++ to work with unicode and > you will contribute > better make_cstring function. Currently I'm using string_escapes = re.compile (r'((\\x[a-f0-9][a-f0-9])|(\\*"))', re.I) def make_cstring (s): def replace_escape(m): g = m.group(1) if g.startswith ('\\x'): return g + '""' elif g == '"': return '\\"' else: return g return '"%s"' % hex_escape.sub (replace_escape, repr (s) [1:-1]) This copes with the problem of hex escapes followed by valid hex characters and with embedded quotes. > > > Can I ask you something? > > Could we switch to one of the mailing lists: pygccxml of boost.python? > I'd like my answers > to be available to other users too. at your request :-) > > It seems that you found work around to "pointer to function" problem. > Can you create > small example with explanation how it should be done. May be I will > able to introduce > this functionality to Py++. Well not for any case. Function pointers without instance pointers still can't be exposed for the reasons given in the reference provided by Py++. Function pointers _with_ instance pointers are a different kind of beast. Generally function declarations using this type of callback have exactly one function pointer argument and exactly one void *argument which is forwarded to the callback function. typedef callback_return_type (*callback_t) (callback_args, void *instance, more callback_args); return_type function (args ..., callback_t, more args, void *instance, more args) Functions having this kind of signature may be wrapped like this: callback_return_type wrap_callback_t (callback_args, void *instance, more callback_args) { PyObject *py_instance = reinterpret_cast<PyObject *> (instance); if (py_instance) { try { return (boost::python::call<callback_return_type> (py_instance, callback_args, more callback_args)) } except (...) { } } return some error value; } return_type function_wrapper (PyObject *instance, args, more_args, ...) { return (function (args ..., &wrap_callback_t, more args, instance, more args)); } I'm attaching the generators module I'm currently using ... The generators are called like this: def wrap_functions (self, decls): """ Generate wrappers for functions otherwise not exportable in their current_form @param decls Function declarations to be wrapped """ wrapper_generators = [ callback_wrapper_generator (self), const_byte_wrapper_generator (self) ] finished = False while not finished: finished = True for d in decls: for g in wrapper_generators: cookie = g.applies (d) if cookie: g (cookie) finished = False break > > Thanks. > > -- > Roman Yakovenko > C++ Python language binding > http://www.language-binding.net/ > Cheers, Gottfried

3 4

problem with tkinter gui running in different interpreters
by Andreas Sept. 3, 2006

Sept. 3, 2006

hello, I'm not sure if this is the right place for my question. I have a problem with tkinter running in different python interpreters. I need to separate different python scripts as much as possible. Therefor each script runs in its own interpreter. If only one of the scripts uses tkinter gui and runs the tkinter's mainloop in a created thread, everything is fine. But if more scripts uses this, the whole application with the created dialogs hangs. To solve this only the first script must call tkinter's mainloop(). But thats not an option, because the scripts are independent and must not have dialogs. Thus a script does not know if it is the first which uses tkinter. So the question is: Is it possible to detect from different interpreters whether the tkinter's mainloop is already running or not? Below is the running example code. In main() i want to start multiple dialogs calling startDialog(true), wich does not work. (I'm using boost 1.33.1, MSVC7.1 and Python 2.4.3) Any help would be appreciated, andreas rose void startDialog(bool bCallMainloop) { PyEval_AcquireLock(); PyThreadState* pThreadState = Py_NewInterpreter(); PyThreadState_Swap(pThreadState); char pBuff[] = "Test.exe"; char* Argv[1]; Argv[0] = pBuff; PySys_SetArgv(1, Argv); PyObject* pDict = PyDict_New(); PyDict_SetItemString(pDict, "__builtins__", PyEval_GetBuiltins()); std::string strExec; if (bCallMainloop) { strExec = "\ from threading import * \n\ from Tkinter import * \n\ \n\ class DialogThread(Thread): \n\ def run(self): \n\ label = Label(None, text='hello') \n\ label.pack() \n\ label.mainloop() \n\ \n\ DialogThread().start() \n\ "; } else { strExec = "\ from threading import * \n\ from Tkinter import * \n\ \n\ class DialogThread(Thread): \n\ def run(self): \n\ label = Label(None, text='hello') \n\ label.pack() \n\ \n\ DialogThread().start() \n\ "; } boost::python::handle<> result(PyRun_String(strExec.c_str(), Py_file_input, pDict, pDict)); result.reset(); PyEval_ReleaseThread(pThreadState); } int main(int argc, char** argv) { Py_Initialize(); PyEval_InitThreads(); PyThreadState* pyMainState = PyThreadState_Swap(NULL); PyEval_ReleaseLock(); startDialog(true); startDialog(false); //wait little time to enable user interaction with the dialogs Sleep(10000); PyEval_AcquireLock(); PyThreadState_Swap(pyMainState); Py_Finalize(); return 0; }

1 0

Lost Again! :)
by Nicolas Tessore Sept. 1, 2006

Sept. 1, 2006

Hello, thanks to your helpful replies, I think I got one step closer to understanding how Py++ should work :) I built a python script that dynamically creates a header file including all the libraries from one folder. Fortunately, each class is contained in one single header called <classname>.h, so that creating the template typedefs and instantiations work fine. Now my understanding is still lacking with respect to template functions: I followed the howto-advise and call every function once for instantiation. This works, however I need to control the name that function later has in Python. At the moment I use function pointers (I could not find something like typedef), but they don't seem to make their way into the Boost.Python binding file. --- Now something from my tests: I noticed I often get a error like super(type, obj): obj must be instance or subtype of type. from a condition in decl_wrappers/calldef_wrapper.py (line 309). However, running your GUI utility for a test, this error never occurs. What is my mistake? --- Another problem arises when I try to build an example I created for my lib: I always run into 'boost::python::init' : too many template arguments errors. I had no time to dive deeper into Boost.Python, anyone up for a quick heads-up? --- This is all :D I really appreciate your efforts in helping out, and I am confident Py++ results will soon overtake Swig and pay off the time invested. Regards, N.

2 10

boost python mingw binaries
by Jorge Vargas Sept. 1, 2006

Sept. 1, 2006

hi does anyone plans on distributing binaries for boost_python under windows? I have try to compile it myself many times and fail. Boost and Boost Jam is something new for me, the docs for boost_python are inclined to someone that knows boost and the ones of boost itself have no leads to what to do if something goes wrong. I'm not a windows dev I just want to give an alternative here so all I need is the binary since my only goal here is to make Democracy player compile with free tools on windows. so does anyone has boost python as a binary that works under mingw?

2 3

boost:python::arg and default value
by Roman Yakovenko Sept. 1, 2006

Sept. 1, 2006

Hi. I want to resolve the issue discussed in this thread: http://thread.gmane.org/gmane.comp.python.c++/9878/focus=9881 The short version of the discussion is: class Foo; class Foo2 { friend class Foo; Foo2(Foo *f=0); }; class Foo { Foo(Foo2 *f=0); }; It is not possible to expose both Foo and Foo2 constructors with default values, without usage of some tricks. The main problem is that, when Boost.Python initializes boost::python::arg, it requires type of default value to be registered. I had some free time and took a look on the code. I think, I understand what is going on and how to fix the situation, but still need some help here and there. I see only one possible solution - to add to Boost.Python functionality, that will allow user to control argument default value conversion time. Today, the default value converted to Python during function registration. This happens in boost::python::objects::function class constructor. Solution: 1. To add classes that will define C++ to Python convert time. struct converter_base{ virtual handle<> py_value() const = 0; //const in interface is a hack, objects::function::call member function //has const modifier }; struct default_converter : converter_base{ converts value in the constructor and saves the value in a member variable py_value returns the member variable }; struct on_first_use_converter : converter_base{ saves the C++ value as member variable py_value will convert C++ value to Python on first invocation, will save the result in member variable, after this, it will always return the member variable. }; 2. Change in keyword struct. Today keyword struct keeps function default value as instance of handle<>. This should be changed. keyword struct should keep shared_ptr to coverter_base class instance or it should keep empty shared_ptr. Thus it will be possible to control C++ to Python default value conversion time from objects::function class. 3. There are few changes, that should be done to boost::python::objects::function class. This is the place I have lack of knowledge and the code is a little bit complex and fragile. More over, every additional logic, that will be added here will downgrade performance. There are few changed that should be done to the class. 1. The class should keep all keywords, that has default value converter other than default_converter. It also should save keyword position. 2. In constructor, when we register function keyword arguments, we should skip initialization of default value, for converters other than default_converter. 3. Now, the only change left is to modify function::call method. Unfortunately I can not write the working code - lack of knowledge( or sleep ). I'll be glad, if somebody can help me here. The main problem, is that some how I should pass to the function default values and I don't exactly understand how I should do that. I attached the modified files. What do you think about those changes? -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/

2 3