FS#21346 - [tint2] tint2conf

Attached to Project: Community Packages
Opened by Max Eng (maksipes) - Tuesday, 19 October 2010, 18:54 GMT
Last edited by Stefan Husmann (stefanhusmann) - Thursday, 28 October 2010, 21:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Stefan Husmann (stefanhusmann)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the upgrade python tint2conf displays an error when trying to edit themes and the editor will not start. In this case, /usr/bin/tintwizard.py works fine.

Additional info:
* package version(s)
community/tint2 0.11-2
extra/python 3.1.2-2
extra/python2 2.7-2
extra/pygtk 2.22.0-3

* config and/or log files etc.

cmd python /usr/bin/tintwizard.py '/home/max/.config/tint2/default.tint2rc' &
File "/usr/bin/tintwizard.py", line 2206
print NAME, VERSION
^
SyntaxError: invalid syntax


Steps to reproduce:
Run tint2conf and press button "Show properties"
This task depends upon

Closed by  Stefan Husmann (stefanhusmann)
Thursday, 28 October 2010, 21:12 GMT
Reason for closing:  Fixed
Comment by B.Vasilyev (bob_art) - Tuesday, 19 October 2010, 20:18 GMT
Hi, yes, i confirm this problem.
Additional info:
* package version(s)
community/tint2 0.11-2
extra/python 3.1.2-2
extra/python2 2.7-2
extra/pygtk 2.22.0-3

~$ tint2conf
and when trying to edit themes, pressed button "Show properties", get error:

cmd python /usr/bin/tintwizard.py '/home/bob/.config/tint2/default.tint2rc' &
File "/usr/bin/tintwizard.py", line 2206
print NAME, VERSION
^
SyntaxError: invalid syntax

~$ /usr/bin/tintwizard.py
run, waiting & responds...

Corrects the position editing ~/.config/tint2/tint2confrc:
sed -i 's/python /usr/bin/tintwizard.py//usr/bin/tintwizard.py/' ~/.config/tint2/tint2confrc

But when create a new file ~/.config/tint2/tint2confrc this error is repeated
Comment by Ionut Biru (wonder) - Tuesday, 19 October 2010, 20:20 GMT
ok, so that needs to be fixed. i'm looking into it now
Comment by Ionut Biru (wonder) - Thursday, 21 October 2010, 00:18 GMT
is it fixed in 0.11-3?
Comment by Stefan Husmann (stefanhusmann) - Thursday, 21 October 2010, 04:27 GMT
Yes. Maybe the local conf has to be recreated.
Comment by mangust (mangust) - Wednesday, 27 October 2010, 19:52 GMT
Hi! I can confirm this problem as well. Maybe the reason is in the recent move to Python 3? going into details....
Comment by Pablo Olmos de Aguilera Corradini (pablox) - Thursday, 28 October 2010, 12:35 GMT
Exactly, one of the changes between python 2 and 3 is that print has to be used as a function, not as a statement that was the old way. So the correct line would be:

Python 2 (old way): print NAME, VERSION
Python 3 (new way): print(NAME,VERSION)

So, the solution is a) the developer checks the code or b) you run the program with python2.

Loading...