Unpythonic and not-very-futureproofed namedtuple import

[GoogleCodeExporter]

The import of namedtuple is done by checking sys.version_info, which doesn't 
properly 
implement python 3.0 checking, and isn't really the pythonic way to import any. 

It's pretty easy to fix, just use exceptions instead of checking versions. 

Original issue reported on code.google.com by foo...@gmail.com on 8 Apr 2010 at 5:04

Attachments:

• pylast-fix-namedtuple.patch

[GoogleCodeExporter]

Thank you. I removed that ugly hack altogether. Pylast now is only compatible 
with Python>=2.6.

Original comment by amr.hassan on 5 Jan 2011 at 5:51

• Changed state: Invalid