Re: [boost] Did Boost 1.59.0 change the meaning of "using python : 3.4 : ..." in user-config.jam?

Subject: Re: [boost] Did Boost 1.59.0 change the meaning of "using python : 3.4 : ..." in user-config.jam?
From: Jonathan Wakely (jwakely.boost_at_[hidden])
Date: 2015-08-24 12:04:02

On 24 August 2015 at 17:02, Jonathan Wakely wrote:
> On 24 August 2015 at 16:57, Jonathan Wakely wrote:
>> On 24 August 2015 at 10:15, Vladimir Prus wrote:
>>> Maybe "using python : 2.7" was previously added by bootstrap.sh. If you
>>> still have
>>> 1.58 conveniently available, could you run bootstrap.sh and compare the
>>> generated
>>> project-config.jam with the one in 1.59?
>>
>> Aha, good thinking:
>>
>> --- boost_1_58_0/project-config.jam     2015-08-24 16:54:41.177750798 +0100
>> +++ boost_1_59_0/project-config.jam     2015-08-24 16:55:03.936748390 +0100
>> @@ -15,7 +15,11 @@
>> project : default-build <toolset>gcc ;
>>
>> # Python configuration
>> -using python : 2.7 : /usr ;
>> +import python ;
>> +if ! [ python.configured ]
>> +{
>> +    using python : 2.7 : /usr ;
>> +}
>>
>> path-constant ICU_PATH : /usr ;
>>
>> So with 1.59.0 the python-2.7 config is only added if
>> python.configured is true, but it used to be there unconditionally.
>
> Oops, sorry, of course it's only added if it's *false* :-)

Changed by https://github.com/boostorg/boost/commit/edca8b1e9317dd6f0ffc46536841708be8480e5d