I think “futurize -1 -w SConstruct” would fix everyone’s problems (2.7 is the scons minimum version) but it is of course a problem. I don’t know how you can tell the scons parser to not enable print_function if it’s running in 2.7. Is there a way to disable that __future__ directive for the code that is dealing with the SConstruct files?
— Tim Jenness > On May 25, 2016, at 11:07 , Bill Deegan <[email protected]> wrote: > > Gary, > > Yup. that's expected. > Not sure how to handle this gracefully (besides as Jason suggests some > "official" messaging API for SCons, which also would require time for users > to adjust to). > > Out of curiosity, would 2to3 resolve the issues you ran into? > (In theory it should) > > Other issues might bit chmod bitmasks (though not until they run via py3) > > -Bill > > On Wed, May 25, 2016 at 5:59 AM, Gary Oberbrunner <[email protected] > <mailto:[email protected]>> wrote: > Hi folks; I know I've been out of the loop recently, lots going on. Great > work getting the python 3 stuff in! > > I did just try the default branch (with python2.7 on Windows) and I notice > print statements (not the function, just the statement) in > SConstructs/SConscripts are now syntax errors. This'll probably be a big > change for users. Just FYI. > > -- > Gary > > _______________________________________________ > Scons-dev mailing list > [email protected] <mailto:[email protected]> > https://pairlist2.pair.net/mailman/listinfo/scons-dev > <https://pairlist2.pair.net/mailman/listinfo/scons-dev> > > > _______________________________________________ > 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
