Fix if/elif/elif/... chains without else

[rbrito]

The code has, in many places, many if/elif/elif/..., but they don't end with elses.

This is a sign of something fishy: at best, it confuses the reader that is left thinking: "why are the other cases not treated"; at worst, it leads legitimate bugs.

One quick'n'dirty, not-really-a-solution, measure is to give each such chains an else statement that simply logs things (using the logging infrastructure already in place) when things go wrong (so that we know that there are cases that we are not treating). This may be a measure for the short-term release of version 1.5.

Alternatively, in non-release versions, we can (and should) throw exceptions whenever something reaches such an else clause that we don't know yet how to treat, so that the problems become evident upon running the program and trying to get work done.

[markeyev]

Let me code it for you.

[asifurrahaman754]

hey is this solved? i would like to work on this

[programmin1]

hey is this solved? i would like to work on this

Look for "if" cases and log a warning/error in else case if applicable?

Honestly if you want to work on something I think porting it to all work on the latest Python3 would be a better use of time.

Please see this repo which is actually the main repo - https://github.com/programmin1/tunesviewer/tree/Python3