On Sat, Feb 23, 2013 at 2:22 AM, Gary Oberbrunner <[email protected]>wrote:
> > > > On Fri, Feb 22, 2013 at 5:53 PM, anatoly techtonik <[email protected]>wrote: > >> On Fri, Feb 22, 2013 at 9:42 PM, Russel Winder <[email protected]>wrote: >> >>> On Fri, 2013-02-22 at 18:10 +0300, anatoly techtonik wrote: >>> […] >>> > Every construct of Python 2.x that is not compatible with Python 3 will >>> > give errors - print statements is the most obvious. >>> >>> Not entirely true. print statements/function calls call be written to >>> be Python 2 and Python 3 compliant, or: >>> >>> from __future__ import print_function >>> >> >> You misused the context. It is not about using print("") in Python 2 - it >> is about using print "" in Python 3, which is just what happen when users >> will try to use old SConstruct files with Python 3. >> > > Oh, well sure. Of course people have to port all their python code to > python3 before they switch to using python3, and that includes SConstructs > and all related files. I thought you were talking about something much > more serious than that. > Nothing can be more serious than a situation where user will be trying to run scons 3 on a SConstruct 2 file or scons 2 on a ported SConstruct 3. These are not compile / build errors. These are not SCons errors either. These are transient errors that one user system has Python 3 "scons" binary and another has Python 2 "scons". These are two different programs with two different incompatible formats of scripts. Even though they are named the same. What can be more serious than pretending that it is the same program?
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
