On Sun, 2013-09-22 at 13:33 -0400, Gary Oberbrunner wrote:
> OK, I ported all of Neal's work onto a python3-port branch in the main
> SCons repo.  I made an initial commit with just the 2to3, then added the
> rest of his initial manual changes, and then cherry-picked all the rest of
> his commits onto that branch.
> 
> This is now the branch where all python3 work should be done.  I think it's
> a good start.  Many tests currently don't pass in my Python 2.7.2 (on
> Ubuntu 11.04); mostly str/unicode type errors so far.  Neal, did you run
> the tests on python2?  Did things work for you?

To date I have kept the D tooling variant of SCons as a separate
repository using the default branch. This turns out to work fairly well,
pending someone telling me when I can propose a merge into the mainline,
which should have happened months ago ;-)

Now with multiple branches how is one supposed to manage the differences
so that the D Tooling appears in the Python 3 branch as well as the
default branch?

Thanks.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[email protected]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev

Reply via email to