> OK, I'll check in your suggested change.
Great, I see it in the trunk now. Thanks!
Austin
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
Hi Austin,
> I haven't directly tested it, but as I understand things there is only
> one built-in integral type (int) in python3:
>
> http://docs.python.org/release/3.0.1/whatsnew/3.0.html#integers
>
> If/when I get a chance, I'll try to answer this question a bit more
> authoritatively.
> I've made this change locally, and it seems to fix things. Does this
> seem like the correct fix? If so, how do I get a patch to the right
> people (or at least ask them to make this change)?
>
> Austin
>
There is a ticket in boost for this
(https://svn.boost.org/trac/boost/ticket/4627) where
On Thu, Dec 23, 2010 at 12:49 PM, Ralf W. Grosse-Kunstleve
wrote:
> - Original Message
>
>> I'm currently trying to build boost-1.45 against python-3.1.3 on win64
>> (visual studio 2009 sp1). This build is failing because
>> boost/python/converter/builtin_converters.hpp is using APIs th
- Original Message
> I'm currently trying to build boost-1.45 against python-3.1.3 on win64
> (visual studio 2009 sp1). This build is failing because
> boost/python/converter/builtin_converters.hpp is using APIs that have
> been removed from python3 without checking the python version;
I'm currently trying to build boost-1.45 against python-3.1.3 on win64
(visual studio 2009 sp1). This build is failing because
boost/python/converter/builtin_converters.hpp is using APIs that have
been removed from python3 without checking the python version; at
lines 138 and 144 PyInt_FromLong is
