Boost C++ Libraries: Ticket #5643: Python 3.2 compiling error ( PyUnicodeUCS2_AsWideChar )

pelotoescogorciao@… — Sat, 25 Jun 2011 18:43:15 GMT

Btw, that's in VS2010 SP1.

component changed; owner set

Steven Watanabe — Sun, 16 Oct 2011 18:12:29 GMT

owner set to Ralf W. Grosse-Kunstleve
component None → Python

owner changed

Ralf W. Grosse-Kunstleve — Mon, 17 Oct 2011 04:57:21 GMT

owner changed from Ralf W. Grosse-Kunstleve to Stefan Seefeld

Stefan, are you set up to test against Python 3? If not, please re-assign to me and I'll see what I can do (I don't normally use Python 3).

anonymous — Mon, 17 Oct 2011 13:34:00 GMT

Ralf,

I may be able to help, but right now I'm getting stuck in a bunch of errors, so I'm not sure how much effort it will take to get started. I just fixed a Python3 compatibility bug in bootstrap.sh, but there appears to be more. After bootstrapping with --with-python=/usr/bin/python3, I see compilation lines with '-I/usr/include/python3.2', resulting in errors like 'pyconfig.h: No such file or directory'. And indeed, on my system (Fedora 15) there is a '/usr/include/python3.2mu/pyconfig-64.h', which means that both the build system as well as the boost.python headers need to be adjusted. (Note that this is the first time I attempt to build boost.python with Python3.)

This looks like there is quite a bit more to fix than a single test failure, and I'm not sure I'll have enough time to address this.

Stefan Seefeld — Mon, 17 Oct 2011 13:34:52 GMT

(sorry, that comment was from me. I hadn't realized I wasn't logged in.)

status changed; resolution set

Ralf W. Grosse-Kunstleve — Mon, 17 Oct 2011 23:31:34 GMT

status new → closed
resolution → duplicate

Looks like this is a dup of #4994, fixed already in April 2011:

% svn log -v -c71050

r71050 | rwgk | 2011-04-06 14:32:59 -0700 (Wed, 06 Apr 2011) | 1 line Changed paths:

M /trunk/libs/python/src/converter/builtin_converters.cpp

libs/python/src/converter/builtin_converters.cpp: Python 3.2 compatibility, based on patch by Matthew Bradbury, fixes issue #4994