Indeed.
SCons does have a deprecation cycle:
https://github.com/SCons/scons/wiki/DeprecationCycle
That said it generally doesn't apply to non-public API's.
But, since it should be fairly trivial to support backwards compat for a
deprecation cycle, it seems worth doing.
On Sat, Mar 31, 2018 at 12:15 PM, Andrew C. Morrow <
andrew.c.mor...@gmail.com> wrote:
>
> I took a quick look through the MongoDB SCons setup, and I found once
> place where we call get_ninfo. I agree that changing these to have clearer
> names would be helpful, but it does feel like leaving in the old property
> names / accessors would be useful for some period of transition.
>
> On Wed, Mar 28, 2018 at 9:27 PM, Jason Kenny wrote:
>
>> I am 😊 and I would like this change myself. Can you make a property
>> with the old value for compatibility
>>
>>
>>
>> Jason
>>
>>
>>
>> *From:* Scons-dev *On Behalf Of *Bill
>> Deegan
>> *Sent:* Wednesday, March 28, 2018 8:22 PM
>> *To:* SCons developer list
>> *Subject:* [Scons-dev] Renaming Node's .binfo and .ninfo attributes
>>
>>
>>
>> Greetings,
>>
>>
>>
>> I'd like to rename them as follows so they're more easily comprehensible
>>
>> .binfo -> .build_info
>>
>> .ninfo -> .node_info
>>
>>
>>
>> Thoughts?
>>
>> Reasons not to change?
>>
>>
>>
>> Is anyone reaching that far into the Nodes?
>>
>>
>>
>> -Bill
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
