Certain common exceptions should present the user with a readable, helpful
error message instead of Python tracebacks. Namely, OSErrors when performing
filesystem operations (copy, move, delete) and MusicBrainz API errors should be
handled during import.
The error messages should contain context about what when wrong. For filesystem
operations, the files involved should be printed. For MusicBrainz API errors,
the search terms should be shown. This will eliminate guesswork in deciding
which album/file caused the problem.
Implementation strategy: For the filesystem operation helpers in beets.util,
introduce new exception classes that inherit from OSError.
Original issue reported on code.google.com by adrian.sampson on 17 May 2012 at 6:54
Original issue reported on code.google.com by
adrian.sampson
on 17 May 2012 at 6:54