[Scons-dev] SCons default branch open for python 2.7/3.x work. Please submit pull requests

[William Blevins]

Two Questions,

1. Are we working out of scons__python3 or merging scons__python3 and
working there?

2. Many of the failing tests are from embedded code blocks in the tests
which futurize and six didn't update automatically. Should the update
process here be "make the embedded code its own file when reasonably
possible" or "just make minimal updates for now"?

V/R,
William



On Sun, Apr 10, 2016 at 12:25 AM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> All,
>
> It's (finally) that time.
> Please submit small pull requests if possible, rather than one with a
> million files/changes.
> (AIU) Bitbucket doesn't handle huge pull requests very well.
>
> I'll be setting up a python 3 buildslave.
>
> We'll be using futurize (If I remember correctly), how do we want to
> handle getting that package (and any requirement's it pulls in) installed?
> Embed? Add to setup.py? Other
>
> -Bill
>
> _______________________________________________
> 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/20160410/0f97d01d/attachment.html>