[Scons-dev] Announcement: Core changes for v2.4 ahead, Switching the Node class to using slots...

[Kenny, Jason L]

Hi dirk, 

So far I ran the gold tests in Parts I have. They all passed on windows. I need to test other systems, and I want to run it against our vtune build. If something would go wrong, it would be there...

Jason

-----Original Message-----
From: Scons-dev [mailto:scons-dev-bounces at scons.org] On Behalf Of Dirk Bächle
Sent: Saturday, March 28, 2015 2:15 PM
To: SCons developer list
Subject: Re: [Scons-dev] Announcement: Core changes for v2.4 ahead, Switching the Node class to using slots...

Hi Alexandre,

On 02.03.2015 09:06, alexandre.feblot at gmail.com wrote:
> Hi Dirk,
>
> About those new interfaces for accessing node attributes that may get initialized lazily, do I understand here the consequences properly?
>
> - Using directly a_node.path or a_node.abspath *must* be replaced in 
> all SConstructs/SConscripts by the new interfaces if we wan’t them to 
> keep working properly
> - This lets us with 2 solutions:
>     1- Do these changes in all our product maintenance branches, and even each time we need to checkout again an old tag we want to compile again.
>     2- Keep an old Scons 2.3 to build our old code, and change our build infrastructure to be able to have different SCons paths, so we can chose the proper one.
>

as you suggested, I implemented a simple backward compatibility layer using the "__getattr__" method. It's checked in to the same development branch "switch_to_slots" now. I also measured the speed of the new revision against the previous approach, and couldn't find any major impact.

It would be very helpful if you could try and run this latest version against your production code. Please give us some feedback about whether this would work for you, and allows a flawless transition to the new version v2.4.

Best regards,

Dirk

_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev