[Scons-dev] SCons and Python 3

[Bill Deegan]

Tim,

On Wed, Sep 9, 2015 at 10:52 AM, Tim Jenness <tjenness at lsst.org> wrote:

>
> On Sep 9, 2015, at 10:49 , Bill Deegan <bill at baddogconsulting.com> wrote:
>
> SCons supports  >=2.7 <3.0
>
> As far as I know, the idea was to not break 2.6 if it was reasonable not
> to, but no guarantee.
> Clearly starting work on 2.7 & 3.0 compatible source code would mean 2.6
> would be dropped entirely.
>
>
> The scons release notes are very specific:
>
>
> This will be the last release to support Python versions earlier than 2.7,
> as we begin to move toward supporting Python 3.
>
> Which reads to me that 2.6 is being dropped and python 3 is to be
> supported.
>

This doesn't conflict with what I wrote in any way.

A guarantee that it will work with 2.6 has been removed.  As I said above,
if a change breaks 2.6 (in the recent past) and there was an equivalently
good way to code it which didn't break 2.6, we'd try to use that.   That
said, I don't think this came up very often.
And as I said above that, shall we say, suggestion is no longer in effect.

At some point (undefined as in no hard commitment on the date of a release
which will work with 3.x) in the future 3.x will be supported.

We've got a fairly big change in default (slots), which should released
sometime in the near future.
Then we've got another larger functional patch (improved cross language
scanners, if it's ready).
Also a fix for some issues with versioned shared librareis, and 3.x work
should happen thereafter.
After that I expect we'll start moving the code to 3.x and 2.7.x compat.

Anyone want to volunteer some buildslaves for 3.x?

-Bill





>
> —
> Tim Jenness
>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150909/0a6dea35/attachment.html>