Compiling Open9x via make all - python scripting error...

[GoogleCodeExporter]

Which board (stock / gruvin9x / sky9x) are you using?
stock

What is your open9x FW version?
r2050

What is your open9x EEPROM version?
r2050

What steps will reproduce the problem?
1. while compiling the outpus shows a nasty python error

What is the expected output? What do you see instead?
SyntaxError: invalid syntax
>>> print test
  File "<stdin>", line 1
    print test
             ^
SyntaxError: invalid syntax

Please provide any additional information below.

I fixed it with correcting img2lbm.py in the following way:

print ("wrong argument", sys.argv[3]) 'with the brackets

other wise it throws a syntax error...

Original issue reported on code.google.com by hanno.dahlhaus on 10 Mar 2013 at 2:16

[GoogleCodeExporter]

What python version, and on what platform?

Original comment by bernet.a...@gmail.com on 10 Mar 2013 at 3:22

[GoogleCodeExporter]

Python 3.3.0-3 on ArchLinux. After adding the brackets the syntax error was 
gone...

Original comment by hanno.dahlhaus on 10 Mar 2013 at 4:45

[GoogleCodeExporter]

Convert icons from png to lbm:
python ../util/img2lbm.py icons.png icons.lbm bmp
  File "../util/img2lbm.py", line 103
    print "wrong argument", sys.argv[3]
                         ^
SyntaxError: invalid syntax

That is the original output I got...

Original comment by hanno.dahlhaus on 10 Mar 2013 at 4:46

[GoogleCodeExporter]

fyi http://docs.python.org/3.0/whatsnew/3.0.html

Original comment by hanno.dahlhaus on 10 Mar 2013 at 4:49

[GoogleCodeExporter]

Thanks for the link!

Original comment by bson...@gmail.com on 10 Mar 2013 at 4:58

• Changed state: Fixed

[GoogleCodeExporter]

But why 'make all' calls the script with a wrong argument?

Original comment by bson...@gmail.com on 10 Mar 2013 at 5:09

[GoogleCodeExporter]

I don't think it calls it with a wrong argument, but python just fails before 
it even gets to run the script because of the syntax error!

Original comment by bernet.a...@gmail.com on 10 Mar 2013 at 6:57

[GoogleCodeExporter]

Ok it's because it first checks for evident syntax errors, then the pb is 
fixed. Thanks!

Original comment by bson...@gmail.com on 10 Mar 2013 at 7:18