[python] still compile error using pyhton 3.x
Hi, since 1.44 boost python does not compile anymore using python 3.x (after a GSOC project it worked fine with python 3.1). I reported this after the 1.44 release and i thought someone had fixed it. This is really sad to see this great library not working anymore. These are the errors generated: compile-c-c++ e:\devel\_ext\boost_out_64\out\boost\bin.v2\libs\python\build\msvc-10.0\debug\address-model-64\threading-multi\object\function_doc_signature.obj function_doc_signature.cpp E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(138) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2065: 'PyInt_Type' : undeclared identifier E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C2039: 'PyInt_FromLong' : is not a member of '`global namespace'' E:\devel\boost_1_45_0\boost/python/converter/builtin_converters.hpp(144) : error C3861: 'PyInt_FromLong': identifier not found E:\devel\boost_1_45_0\boost/python/detail/caller.hpp(55) : warning C4244: 'return' : conversion from 'Py_ssize_t' to 'unsigned int', possible loss of data libs\python\src\object\function_doc_signature.cpp(287) : warning C4244: 'initializing' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data libs\python\src\object\function_doc_signature.cpp(294) : warning C4244: '=' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data libs\python\src\object\function_doc_signature.cpp(303) : warning C4244: '=' : conversion from 'boost::python::ssize_t' to 'int', possible loss of data
On Sun, Nov 21, 2010 at 7:51 PM, Christopher Lux <christopherlux@gmail.com> wrote:
Hi, since 1.44 boost python does not compile anymore using python 3.x (after a GSOC project it worked fine with python 3.1). I reported this after the 1.44 release and i thought someone had fixed it. This is really sad to see this great library not working anymore.
These are the errors generated:
It's probably best to create a Trac ticket for this, assigned to the 'python' Component, so that it can be tracked appropriately by the Boost.Python maintainers. It would be best to indicate the platform, and the steps to reproduce. The Trac for Boost is at https://svn.boost.org/trac/boost/ HTH -- Dean Michael Berris deanberris.com
At Sun, 21 Nov 2010 20:15:26 +0800, Dean Michael Berris wrote:
On Sun, Nov 21, 2010 at 7:51 PM, Christopher Lux <christopherlux@gmail.com> wrote:
Hi, since 1.44 boost python does not compile anymore using python 3.x (after a GSOC project it worked fine with python 3.1). I reported this after the 1.44 release and i thought someone had fixed it. This is really sad to see this great library not working anymore.
These are the errors generated:
It's probably best to create a Trac ticket for this, assigned to the 'python' Component, so that it can be tracked appropriately by the Boost.Python maintainers. It would be best to indicate the platform, and the steps to reproduce.
The Trac for Boost is at https://svn.boost.org/trac/boost/
Also, I think the biggest problem is that none of our regression testers are testing against Python 3.x. If you would like to volunteer some resources to run these tests it would help ensure that the code keeps working. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On 11/21/10, David Abrahams <dave@boostpro.com> wrote:
Dean Michael Berris wrote:
It's probably best to create a Trac ticket for this, assigned to the 'python' Component, so that it can be tracked appropriately by the Boost.Python maintainers. It would be best to indicate the platform, and the steps to reproduce.
The Trac for Boost is at https://svn.boost.org/trac/boost/
Also, I think the biggest problem is that none of our regression testers are testing against Python 3.x. If you would like to volunteer some resources to run these tests it would help ensure that the code keeps working.
I created a ticket (there was no selection for the python component): https://svn.boost.org/trac/boost/ticket/4873 Regards -chris
AMDG On 11/21/2010 5:21 AM, Christopher Lux wrote:
On 11/21/10, David Abrahams<dave@boostpro.com> wrote:
It's probably best to create a Trac ticket for this, assigned to the 'python' Component, so that it can be tracked appropriately by the Boost.Python maintainers. It would be best to indicate the platform, and the steps to reproduce.
The Trac for Boost is at https://svn.boost.org/trac/boost/ Also, I think the biggest problem is that none of our regression testers are testing against Python 3.x. If you would like to volunteer some resources to run these tests it would help ensure that
Dean Michael Berris wrote: the code keeps working. I created a ticket (there was no selection for the python component):
I believe that the trac component is Python, and the sort is case sensitive. In Christ, Steven Watanabe
participants (4)
-
Christopher Lux -
David Abrahams -
Dean Michael Berris -
Steven Watanabe