txsjoinatoroutputfile.py exception syntax

Bug #676617 reported by Bozleclerc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tuxtremsplit
Fix Released
Undecided
Guillaume Hain
3.x
Fix Released
Undecided
Guillaume Hain

Bug Description

env:
Ubuntu 2.6.31-22-server x86_64
python 2.5

I got an error while i try to use tuxtremsplit:
File "/usr/lib/pymodules/python2.5/tuxtremsplit/core/txsjoinatoroutputfile.py", line 55
    except IOError as e:
                    ^
SyntaxError: invalid syntax

i just replaced 'as' with a ',' and it worked.

Revision history for this message
Guillaume Hain (zedtux) wrote :

Thanks for reporting bug.

Could you provide a complete test case ?
How did you do to have it fail ?

Changed in tuxtremsplit:
status: New → Incomplete
assignee: nobody → zedtux (zedtux)
Revision history for this message
Bozleclerc (boz-yopmail) wrote :

I had an old version (can't remember, but it was an alpha) of tuxtremsplit.
So yesterday I add your repository (ppa:zedtux/tuxtremsplit), update it, remove my previous tuxtemsplit then install the new one.
at the end of the installation process i had the message displaying the syntax error with the 'as'.
I tried to launch tuxtremsplit, got the same message.
I edit the txsjoinatoroutputfile.py, remove the 'as' at line 55 and replace it with a coma.
That is all what i did...

Revision history for this message
Guillaume Hain (zedtux) wrote :

Okay, thank you for details.

As I can see, you're using python 2.5. It should be the origin of the issue. It's very odd that this happened during installation step.

I will install a Virtual Machine with hardy (seems to be the version with python 2.5) and check the issue.

Revision history for this message
Guillaume Hain (zedtux) wrote :

This bug report helped me to fix another bug:

When output file creation failed, TuXtremSplit doesn't care about exception :s
Now it's fixed with commit http://bazaar.launchpad.net/~zedtux/tuxtremsplit/trunk/revision/166

Revision history for this message
Guillaume Hain (zedtux) wrote :

The commit also fixed this bug report. :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.