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

Hi, On 10.04.2016 20:56, Bill Deegan wrote: All, Here's what I propose. 1. Merge scons_python3 down to default. It's o.k if it's broken for a bit. We can always do bug fixes out of rel_2.5.0 branch if needed and merge those down. 2. I'm o.k. with many tests failing when merged down to

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

On Sun, Apr 10, 2016 at 3:52 PM, Russel Winder wrote: > On Sun, 2016-04-10 at 13:02 +0100, William Blevins wrote: > > Two Questions, > > > > 1. Are we working out of scons__python3 or merging scons__python3 and > > working there? > > With SCons 2.5.0 released and a

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

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

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

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