As a side-note, I don't foresee 2.5.0 breaking 2.6 compatibility either. On Wed, Dec 2, 2015 at 6:59 PM, Dirk Bächle <[email protected]> wrote:
> Hi Tom, > > On 02.12.2015 18:59, Tom Tanner (BLOOMBERG/ LONDON) wrote: > >> It's not dead and buried where I work yet. I'm working on it. >> >> > and you'll be able to continue working on it, with the current SCons > version that you can stick to. > > The deprecation cycle for Python 2.6 compatibility has been how long > now...a year or so? I'd have to look it up, but we definitely did > everything we could by backporting stuff for 2.6 for a very long > time...even though it was already officially deprecated. > It's time to make a clear cut now, in order to finally get ready for > Python 3.x...and that's what we'll do. > > Best regards, > > Dirk > > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
