Re: [Fuego] [PATCH] python3: Use python3 in the scripts to fully migrate

Just to follow up on this...

> -----Original Message-----
> From: Bird, Tim
>=20
...
> Finally, before changing the shebang in all the parser.py scripts, I'd li=
ke to implement
> the compatibility changes first.  That is, change all the print statement=
s to be parenthesized,
> BEFORE changing the shebang lines.  This way the code is never left in a =
faulty state
> (such that a git bisect would fail).

I have done this for python print statements I parser.py and create_xml*.py=
 and fuego_test.sh
scripts, under the fuego-core/tests directory.

These have been pushed to the master branch of fuego-core on bitbucket.

I found a surprising number of other oddball cases where the python interpr=
eter is used,
can called directly.  There's one I especially worry about for your case in=
 Functional.LTP.
But maybe you've already deal with this.  It looks like ltp_process.py does=
n't have any
unparenthesized print statements, but it does have a '/usr/bin/python' sheb=
ang line.

Did you already convert this shebang at your site?

I'm working on my PYTHON_EXE idea next, and I'll let you know how it goes.
 -- Tim