Re: Minimum Version for Tools

And that's what I get for thinking too much along the style guide for a work project.  I completely forgot that a good old try/except would do the trick.

Thanks,

Keith

On 2021-06-20, Bill Deegan wrote:
>I'd second Thomas' answer.
>Just try/except for those things you use which change.
>There aren't many that are in common usage.
>In general we go through a deprecation cycle for items listed in the
>manpage.
>Internals aren't subject to such, but will be mentioned in the CHANGES.txt
>and RELEASE.txt.
>
>-Bill
>
>On Sun, Jun 20, 2021 at 5:35 AM Mats Wichmann <[email protected]> wrote:
>
>> On 6/20/21 5:40 AM, Thomas Berg wrote:
>>
>> > I did wonder if this API breakage was accidental though, or if it was
>> > intentional.
>>
>> Intentional, but perhaps not completely well-considered.  The intent was
>> to remove conflicts with names Python already uses - having Warning as
>> the base class of all Python warnings and also as the name of the base
>> class of all SCons warnings had some potential for confusion when used
>> unqualified - obviously there's no issue if every single mention of the
>> internal one is spelled SCons.Warnings.Warning.  The same change was
>> made to EnvironmentError, the internal one is now SConsEnvironmentError.
>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> [email protected]
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>

>_______________________________________________
>Scons-users mailing list
>[email protected]
>https://pairlist4.pair.net/mailman/listinfo/scons-users


-- 
Keith F Prussing