Skip to content

PyWeather 0.6.2 beta
Compare
Choose a tag to compare
@o355 o355 released this 25 Sep 02:23
· 357 commits to master since this release
0.6.2-beta
2d9a4fd

The moment you've been waiting for! PyWeather 0.6.2 beta. Featuring more awful jokes and more bug fixes than features.

Before I list all changes, this will be the last update that includes new data types. I don't really see calling webcam images a data type (if I decide to implement this feature), but that's beside the point. From here on out, cool features are coming to PyWeather, so sorry if this release is a little boring. Anywhom, let's get to the changelog!

New features (and removals):

  • Ever wondered what the weather was yesterday? Forgot to go outside? Fear no more! Yesterday's weather has been added, thanks to @ModoUnreal. Truly a life-changing feature.
  • Hurricane data has now been added to PyWeather, so that's cool.
  • Ever wondered when high tide will occur? PyWeather can help you answer that question. Oh, right, tide data has been added, and you can view it on your summary screen! (Quick note, for cities on the ocean, you might not be able to view low/high tide data. I had an issue with NYC not showing low/high tides.)
  • You can now separately configure 36-hour and 10-day hourly cache times. Please note, the 36-hour cache option may be confused with 3-day in the code. Thanks again to @ModoUnreal for coding this in!
  • You know that pesky geocoder fiasco from 0.6.1 beta? That's gone. PyWeather Setup will now automagically detect which scheme you can use, and the same goes for when you update to 0.6.2 beta.
  • No one asked, and I delivered! You can now enter non-whole numbers for cache times in the setup file!
  • In the sad event that your version identifier file is missing, you can now manually define the version you're upgrading to in the configupdater script.
  • I added messages for up-to-date and no matching version messages in the configupdate script. Please be proud.
  • Another script has sadly passed away (deleted), the configdefault script. The script really isn't needed, as the configsetup script does the same thing!
  • Minor UI changes.

Now, thanks to the brand new, anti-critical bug QA process, there are indeed more bug fixes than features. Who cares! Stability > New stuff.

Bug fixes:

  • Fixed a critical bug where if geopy wasn't installed before setup, PyWeather Setup would install geocoder INSTEAD of geopy, and throw an error. My bad, my bad.
  • Fixed a bug where radar cache variables weren't globalized in the function. Sad! Wait, no, Tracebacks that didn't crash PyWeather!
  • Fixed a bug where if your config file failed to load, cache times were set insanely low. Who forgot to multiply cache times by 60? This guy! Maybe some people enjoyed having alert data getting refreshed every 5 seconds.
  • Fixed a bug where basically the key backup portion of the setup file didn't work at all! In addition, I also fixed a bug where if you entered nothing, PyWeather Setup throw an error (thanks to @creepersbane for reporting the issue!)
  • Fixed a bug where if your config file failed to load, enter to continue prompts were disabled. That's no fun when looking at 10-day hourly forecasts!
  • Fixed a bug where at the bypassing radar confirmation section of setup, if you entered "yes" or "no" PyWeather Setup would crash. Entering nothing would not trigger the bug.
  • Fixed a bug where you weren't able to exit the summary screen of historical data. That's no fun being forced to look at 6 iterations of hourly data!
  • Fixed a bug where wind chill data in Celsius in historical hourly data was displayed with the unit "kph". Folks, the wind chill on January 5, 2016 in our town was 25 kph. Wait, what? That's not right!
  • Fixed a bug where the 10 day forecast cache time was accidentally running off of the hourly cache time. Oops!
  • Fixed a bug where if there was no moonrise data, PyWeather didn't catch the lack of data, and a crash occurred. Proper data validation has been added to sunrise, sunset, moonrise, and moonset data as a matter of a fact.
  • Fixed a bug where if you set alerts data not to be prefetched at boot, when you viewed detailed alerts data, PyWeather would crash.
  • Fixed a bug where if you had 10-day hourly prefetch enabled at boot, when you wanted to quickly view detailed 10-day hourly information PyWeather would crash. That's ironic!
  • Fixed a potential bug where the configupdate script might not work at all (especially if you manually updated your version identifier file yourself). I changed the code to now look for a version number, instead of an exact match.
  • Fixed an odd bug where yesterday precipitation data could say "T in". I made sure the "T" won't appear again (a.k.a added a data check)
  • Fixed a bug where if some (or all) almanac data wasn't available, PyWeather would crash. This also relates to fixing an issue where PyWeather wouldn't catch a blank data value for normal high/normal low in the almanac. Thanks to @ModoUnreal for reporting this!
  • Fixed a "bug" where if you didn't have a connection to raw.githubusercontent.com (or didn't have an internet connection at all) with the updater enabled, PyWeather wouldn't work. This was intentional code added a while ago, but I guess I didn't see DNS blocking of the domain in sight. Thanks to @creepersbane for reporting the issue!

Other changes:

  • @ModoUnreal is now an awesome contributor!
  • The setup file will now forcefully write out a new version identifier file when run.

There you have it, PyWeather 0.6.2 beta. A special thanks to @ModoUnreal for some amazing contributions to this version of PyWeather!

Updating PyWeather

It isn't a PyWeather update without a broken updater! Anyways, the built-in updater will complete everything, but fails on the final print statement on most platforms. Enter "No", then exit PyWeather afterwards. This will be fixed, but you'll have to deal with this once 0.6.3 beta comes out.

Remember when I forgot to gitignore the versioninfo.txt file last version? That also does the domino effect here. When you update to PyWeather 0.6.2 beta, you'll need to manually input "2" in the configupdate file if you come from PyWeather 0.6.1 beta (non-https or https), and "1" if you come from PyWeather 0.6 or 0.6.0.1 beta.

Anyways, here's how to update (0.6 beta and above)

Without git, download the release below, drag all files into your PyWeather folder (allow the overwrite!), and run configupdate.py. Make sure you enter "1" or "2" depending on which version you're updating from.

Git users:

git fetch
git stash - Do this even if you haven't made any changes, better be safe than sorry!
git checkout 0.6.2-beta

Run configupdate.py afterwards.

If you come from PyWeather 0.5.2.1 beta and earlier, you'll need to reinstall PyWeather, so follow the instructions on the front page.

The built-in updater should work, you'll still need to enter "1" or "2" depending on which version you're updating from.

Updates on PyWeather

First off, I'm back in school (ugh), but I have a study coding hall, so hurray! I've also been working on other projects, so that contributes to the long wait between releases.

Starting with this version, I'm doing an extensive QA on each new version of PyWeather, on multiple platforms, in different ways. This is partially why 1/2 the commits are bug fixes, and why the delay between releases went up too.

Wondering about me? I'm doing great! I managed to do a rescue mission to save my Kerbals on Duna. Anyone got tips on an Eve rescue mission? How much Delta-V do I need?

In other news, PyWeather 0.6.3 beta will start development this week, with lots of awesome, new features. Basically, stuff I actually want to work on. PyWeather 0.6.2 beta is indeed the last release with new data types. It's a little sad, but the initial objective of PyWeather has been completed. I seriously can't wait to start working on new stuff!

And there we have it, PyWeather 0.6.2 beta. It might be a boring release, but I promise to quickly release PyWeather 0.6.3 beta. I'm considering doing RCs for 0.6.3 beta, but that doesn't make sense, it's a release candidate for all I care. Maybe something like PyWeather 0.6.3 beta^2 1?

See you all later in the year!

Also, this is the first non-pre-release release of PyWeather. I feel as if it's deserving thanks to the large QA process.

Assets 3
Loading