Re: no more print statements in SConscripts?

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CG2f1M=0_0YOuFsozR+nZTzK27dRh24HvL=F99Waw97Pg@mail.gmail.com>
Tim,

I think this is a python global flag isn't it?
I don't think you can turn it on and off selectively?

-Bill

On Wed, May 25, 2016 at 11:14 AM, Tim Jenness <[email protected]> wrote:

>
> > On May 25, 2016, at 11:12 , Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
> wrote:
> >
> > Tim,
> >
> > The issue then is that we've migrated the SConstructs/SConscripts in the
> test suite to use print() so we can work on getting py3 also working.
> >
>
> I think those tests can have “from __future__ import print_function” added
> to them and the tests would pass.
>
> My worry is releasing scons v3 and having all the python 2.7 users scream.
> If we can just make it so that the importing code for external files does
> not inherit print_function by default then everyone will be happy.
>
> —
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.