FS#22178 - [boost/boost-libs] Support for Python 3
Attached to Project:
Arch Linux
Opened by Darklighter (Darklighter) - Tuesday, 21 December 2010, 19:27 GMT
Last edited by Ionut Biru (wonder) - Friday, 04 March 2011, 13:12 GMT
Opened by Darklighter (Darklighter) - Tuesday, 21 December 2010, 19:27 GMT
Last edited by Ionut Biru (wonder) - Friday, 04 March 2011, 13:12 GMT
|
Details
Support for Python 3 in Boost.Python has been available
since 1.41.0, but is not enabled in the boost and boost-libs
packages. It can be enabled by creating a user-config.jam
containing the following lines:
using python : 2.7 ; using python : 3.1 ; This will build libboost_python3.so in addition to libboost_python.so. |
This task depends upon
Closed by Ionut Biru (wonder)
Friday, 04 March 2011, 13:12 GMT
Reason for closing: Implemented
Additional comments about closing: boost 1.46 now in testing
Friday, 04 March 2011, 13:12 GMT
Reason for closing: Implemented
Additional comments about closing: boost 1.46 now in testing
Comment by Ionut Biru (wonder) -
Tuesday, 21 December 2010, 19:53 GMT
Comment by
Darklighter (Darklighter) - Tuesday,
21 December 2010, 20:51 GMT
Comment by
Thomas Dziedzic (tomd123) - Sunday,
27 February 2011, 05:00 GMT
Comment by
Thomas Dziedzic (tomd123) - Sunday,
27 February 2011, 05:23 GMT
Comment by
Darklighter (Darklighter) - Monday,
28 February 2011, 23:19 GMT
Comment by
Thomas Dziedzic (tomd123) - Tuesday,
01 March 2011, 00:32 GMT
there are downsides after enabling this on
usr/include/boost/python/ ? like breaking compilation on
applications that are using that?
No, the header files don't change after running bjam with the
above lines.
Apparently it isn't as easy as OP said it would be because there
are errors if you enable python3 during build of 1.46 with
python3.2.
Just to make myself more clear. Boost 1.45/1.46 may have been easy
to enable python3.1 support, but since we upgraded to python3.2,
boost might not have had enough time to have updated its codebase
for the new python version. I didn't mean to sound like op is
lying. So I suppose this will either have to wait until boost 1.47
or until upstream patches their code to build with python3.2. Btw,
here are some errors I get when I tried to enable python3.2
support:
http://pastie.org/1612031
Here's the associated ticket and patch:
https://svn.boost.org/trac/boost/ticket/4994
great, please let us know when it gets accepted/applied, Cheers!