Can you estimate the efforts that you spend porting Python 2 SConstruct to Python 3? This info IMHO is very critical for existing SCons users who are not aware of Python 2/3 portability issues. We will have to create a separate porting guide for those SCons users, who are not Python hackers like SCons devs.
On Mon, Mar 10, 2014 at 8:15 PM, Gary Oberbrunner <ga...@oberbrunner.com> wrote: > I plan to merge things in soon. I have some local changes already so > I think I'm the best one to do it. > > On Mon, Mar 10, 2014 at 1:06 PM, Russel Winder <rus...@winder.org.uk> wrote: >> Is it correct that no-one has been keeping the Python 3 branch up to >> date with all the changes that have gone into default? >> >> -- >> Russel. >> ============================================================================= >> Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net >> 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk >> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> http://two.pairlist.net/mailman/listinfo/scons-dev > > > > -- > Gary > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > http://two.pairlist.net/mailman/listinfo/scons-dev -- anatoly t. _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
