Tim, yes, I misread you, thanks for the clarification. Ok, saved for this time. -- Alexandre Feblot
> Le 26 mai 2016 à 01:24, Tim Jenness <[email protected]> a écrit : > > >> On May 25, 2016, at 16:13, Alexandre Feblot <[email protected]> wrote: >> >> >> >> Obviously, not introducing any "api break" would be the best, but I don't >> see where Tim suggests a solution. Tim wrote about "removing print >> statements from his SConscripts", which is exactly the painful case I >> described. >> > > I don’t think I suggested that. I (thought I) was suggesting that the code in > scons that loads the SConscript files should not itself include any print > statements so that there would be no need to enable print_function in that > file. > > For simple prints in that file you also have the option of doing > > print(some_string) > > which works on both 2.7 and 3.x regardless because in 2.7 those parentheses > disappear. It’s only when commas start turning up that you need > print_function enabled. > > — > Tim Jenness > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
