PyWeather 0.5.1 beta

It's been a while, and with each subsequent release, the wait times get longer. But that means more features. And that's good. Here's the changelog for 0.5.1 beta!

• Removes some old code (if verbosity == True) in the separate updater, and key backup scripts.
• PyWeather will now load your backup key in the event it can't load your primary key now. A more advanced version of this with valid key checking will come in 0.5.2 beta!
• Adds the raw traceback output option in the separate updater.
• If you have verbosity turned on, configuration options are now outputted at the start of all scripts!
• A new backup key system has been implemented. The user can now decide what directory they want the key in, but for the sake of simplicity and few errors, the filename will stay static to backkey.txt. (thanks to @ModoUnreal for the PR)
• Changes the non-critical traceback printing function in all scripts from an INFO level to a WARN level.
• The setup file has been caught up with new configuration options present in 0.5 beta.
• PyWeather's updater (integrated & separate) will now show the release tag (if you have it turned on), even if PyWeather is up to date.
• In the setup file, the key reconfirmation is now an infinite loop. You can reconfirm your key forever (if you answer no, of course)!
• PyWeather will now check for "None" precipitation amounts in the 10-day forecast for the current day, and -999 mph winds for the current day in the 10-day forecast.
• Multiline prints in setup.py have been rewritten for code beautification (if that's the right word...) (thanks to @gsilvapt for notifying me of the issue, and for submitting a PR, and for Rhombid on /r/learnpython for a good solution)
• Adds the configdefault.py script, so you can set all configuration options to their defaults.

And, while I was adding new features, bugs got fixed!

• Fixed a bug in which if the config file wouldn't load in the separate updater wouldn't load, the variable showReleaseTag didn't get defined, and presumably PyWeather crashed.
• Fixed a bug in which in the keybackup script, the logger name was the old 0.4.2 name.
• Fixed a bug in which if Wunderground gave intervals greater than 60 minutes apart in historical "hourly" information, PyWeather would only display 24 iterations. This is fixed, but some detection methods got scrapped, so there might be a few UI quirks that I could fix later down the road (loop before the user sees the information)
• Fixed multiple UI bugs in regards to historical hourly information, and 10-day hourly information.
• Fixed a "bug" in which the config file couldn't be loaded, the "error" wasn't properly caught. Turns out, there is no error to catch.
• Fixed a bug in which if the config file couldn't be successfully written to, the error wasn't properly caught.
• Fixed a bug in which the logger name wasn't properly defined in all scripts.

0.5.2 beta is now on the release train, and it contains a cool amount of new features and bug fixes. Get ready.

A quick note, the reason behind the increased delay between releases is, you guessed it, all the new features I'm adding. I'm doing more careful coding, but I'm also not going ham at PyWeather, so the combination of both is to blame for the longer delay between releases.

However, the changelog file is constantly updating with rough ETAs on when stuff will be done. Of course, life may get in the way, and sometimes, I do want to take a break from PyWeather.

Oh, and if you're wondering, I should be "done adding new features" by the end of August. Subject to lots of change, of course!

Updating is simple enough. Git users:
git pull
git checkout 0.5.1-beta.

PyWeather updater, download the latest zip. I'm planning to add support for git updating soon! (0.5.3 beta)

As always, report any pesky bugs you might find.

See you all in another few weeks with 0.5.2 beta!

(of course, some bugs were found while writing this release)