I have found that a significant minority of torrent metafiles begin with a not-so-magic  "d12:_info_length", rather than the expected "d8:announce". While this is not explicit in the spec, it is valid bencode and such files work fine with Transmission, uTorrent and official BitTorrent client.
- Modified torrent metafile validation to allow metafiles starting with "d12:_info_length"
- DRYed out the TorrentProvider class's downloadResult function, which was duplicating code from the parent function, as well as never using Bricky's modified validation code in the parent's _verify_download function
Tweaks to KAT provider:
- Search results are now sorted by number of seeders, so that torrents with more seeders will be prioritized (current order is random).
- Also now discarding torrents with zero seeders.
Adding support for Alternate Scene Names to the KAT provider's search
KAT provider's fuzzy search now works for season searches too
Merge branch 'for_pull_requests' of git://github.com/SoulAuctioneer/Sick-Beard into pullreq9
Better quality choices availabe now, able to match dtvt quality
mechanism a little better.
Undo some changes:
* Inheritance: while it is of course more correct to inherit from
object, this is something that should be done application-wide, and I
think we'll wait for midgetspy's branch to take this step first.
* The downloadResult changes are good, but the reason for overriding
them in torrentprovider was because the base implementation saves first,
then checks.  This can create issues for torrent clients using inotify
for example.
Whitespace changes
Merge branch 'pullreq9'
Merge remote-tracking branch 'upstream/master'