[Scons-dev] Why we need to release separate SCons3 for Python 3

[anatoly techtonik]

On Fri, Feb 22, 2013 at 9:42 PM, Russel Winder <russel at winder.org.uk> 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.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20130223/294d05a5/attachment.html>