On Tue, Sep 17, 2013 at 7:09 AM, Neal Becker <[email protected]> wrote:
> Russel Winder wrote: > > > On Thu, 2013-09-12 at 22:48 +0200, Dirk Bächle wrote: > >> Hi Neal, > >> > >> thanks for all your efforts, trying to get SCons running with Python3. I > >> created a diff of the (current trunk + 2to3) against your repo, please > >> find the patch file attached. > > > > Indeed, definite thanks to Neal for getting things moving. > > > >> Looking at the changes, I think it might be worth a try, and compile the > >> patch into a little fixer script of its own. Then we could continue with > >> our basic development on Python v2.6 or v2.7, but easily create a > >> Python3 version by applying our personal "fixer" and 2to3 on top of it. > >> > >> Just as an idea... > > > > Everyone I know who has gone with the policy of 2.6/2.7 codebase with a > > script to use 2to3 to create a Python 3 version has said "forget it it > > doesn't work". Yes use 2to3 to get a comparator version, but always go > > with a single codebase that works with 2.6, 2.7 and 3.3, i.e. use the > > result of 2to3 to guide editing the codebase that still works under 2.6 > > and 2.7 as well as 3.3. > > > > I am assuming we will put: > > > > from __future__ import absolute_import, print_function, > > unicode_literals, division > > > > as the first line in every file so that we write Python 3.3 that runs > > under 2.6 and 2.7? > > > > At this point, scons does what I need it to do. What needs to be done > includes: > * fix test suite > * support for 2.6? > > I'm afraid I have no motivation to take on either of these tasks. > Hopefully > some others would like to continue the effort? > > Yes. We'll make this happen somehow. Volunteers are of course welcome! And Russel, I think your plan has to be directionally correct. We do have to aim for a single code base (whether it's 26 or 2.7 floor). -- Gary
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
