Will try to do some more on this over the weekend. I got stuck on the weird os.mkinfo problem (still unsolved) and got a bit distracted by Me TV rewrite required to be ready soon so as to watch the 6 Nations games. New DVB-T2 USB sticks arriving tomorrow.
On the really up-side, it appears that "futurize -1" is properly idempotent, making it a lot easier to work with than anything previously. Aim is still to get the code-base working properly, i.e passing all tests, as a Python 2.7 program, so that it can then become the default branch. My thinking here is that if we do not have a separate branch, but instead are evolving default to be Python 3 compatible as a Python 2.7 codebase then Python 3 usage will happen faster. The "down side" is that all Python 2 code must be written with Python 3 compliance from merge time on on, this includes all pull requests. -- 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
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
