Dirk, If we can avoid print in src/engine/SCons/Tool/__init__.py, then each tool can import print_function() if they need/want it?
-Bill On Thu, May 26, 2016 at 1:26 AM, Dirk Bächle <tshor...@gmx.de> wrote: > Hi there, > > On 26.05.2016 03:52, Jason Kenny wrote: > >> I am unclear on what people are suggesting as fixes to the issue. However >> I believe we tweak the way we “load” the Sconstruct we can >> control which print logic is used when python 2.7 is used. I don’t >> believe there is any way to allow the “classic” python 2.7 print >> to work in python 3. >> >> I think if we can allow user of python 2 and SCons to not have their >> files break, that is a win. When using python 3 the users will >> need to update the SConstruct print statements ( or use some API we might >> be able to add). >> > > it just came to my mind that we also have to think a little about the > external tools. They need to get updated too...which is actually more of a > task for each repo owner, but it would be good to have some kind of support > here. > > Regards, > > Dirk > > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev