Skip to content

PyWeather 0.6 beta

Pre-release
Pre-release
Compare
Choose a tag to compare
@o355 o355 released this 28 May 04:14
· 568 commits to master since this release
0.6-beta
13913b1

2 critical bugs was found in PyWeather 0.6 beta, in which new users couldn't properly provision their configuration file, or reset their configuration file. Existing users are not affected by While a workaround to this is using the configsetup.py script, PyWeather 0.6.0.1 beta has been released, and fixed 2 critical bugs. Please update when you can.

Hey! Even though I've been swamped with tests, other projects, and schoolwork, I managed to squeak out a PyWeather release just before things get really busy. Introducing, PyWeather 0.6 beta!

This release is a little unusual, as I mainly focused on under-the-hood changes, and one major feature had to get scrapped for this release. The radar wasn't working properly with the GUI library I wanted to use ("corrupted" .gifs), but it'll be added as an experimental feature in 0.6.1 beta. Anywhom, let's get to the changelog.

  • An about page was added to PyWeather
  • Alerts got added to PyWeather! You can view severe weather alerts for locations in the US/EU, along with detailed information.
  • The option to show release notes in the updater, along with when a new version should come out was added.
  • The "menu" is now purely number based. You can't select options with words anymore, but I feel as if it's a bit better this way.
  • Support for overriding versions was removed, thanks to a huge update I'll detail later.
  • Error catching was added for a bad reverse geolocator fetch.
  • Minor UI changes

Before I get to the biggest changes, let's check out some bug fixes.

  • Fixed a bug where if your backup API key couldn't be found, key validation was entirely skipped. I guess this was intentional, but now if your primary key is still validate, but if your backup key couldn't be loaded at first boot, it'll stop before trying to validate a non-existent key.
  • Fixed a bug where when running configdefault.py, "PYWEATHER BOOT/validateapikey" wasn't reset to it's default value.
  • Fixed a bug where if you enabled update checking at boot, PyWeather would crash due to code not getting up-to-date with the requests library (effected 0.5.2 - 0.5.2.1 beta)
  • Fixed a bug where in historical hourly information, if you had the iteration counter on, it would print in red.

The biggest change in PyWeather 0.6 beta is how the config works. There have been loads of issues in regards to config updating with Git (and the .zip method, too), so I thought I'd solve the issue.

The config works like this now. The config isn't bundled with PyWeather, it's created in the setup script. All scripts have detection methods to detect if a config is provisioned or not.

When updating PyWeather, things work like this. PyWeather will execute a configupdate.py script, which preserves your present settings, but will let you set up new configuration options available in newer versions. Say from 0.6 -> 0.6.2, 4 new options are available, but from 0.6.1 -> 0.6.2, 2 new options are available.

A file gets created in PyWeather's storage folder called "versioninfo.txt", containing your version info. Depending on what version the configupdate detects, it'll make appropriate changes, like such:

if versioninfo == "0.6 beta":
    write 4 config options
elif versioninfo == "0.6.1 beta":
    write 2 config options

After that's done, versioninfo.txt gets updated to what version the user is on, and all is happy and well. A true test of this will come in PyWeather 0.6.1 beta.

Otherwise, those are all the major changes in PyWeather 0.6 beta. Updating to this release is different, and will , so follow the instructions below.

If you update with the .zip method, and likely overwrite files:
You'll want to delete config.ini, and then set up your config again by launching the configsetup.py script in the storage folder. Configure any additional options, and launch PyWeather.

(Git instructions are preliminary. I will have to test these methods after I publish this release)

If you manually update through Git:
Run git fetch, then git checkout 0.6-beta. Make sure you run git stash if you made any local changes to any scripts. Since going this method will automatically delete your existing config, you'll want to run the configsetup.py script in the storage folder. Configure any additional options, and launch PyWeather.

If you use PyWeather's built-in Git updater:
Let the updater do it's thing. It may fail, if it does, enter "No". Afterwards, launch configsetup.py in the storage folder. Configure any additional options, and launch PyWeather.

PyWeather 0.6.1 beta will come out in July, and will also bring some major backbone changes, along with extra features, too. Subsequently, PyWeather 0.6.2 beta is scheduled for release in August, and it'll bring some extra features. These ETAs are very preliminary, and conservative, and are likely to change.

After all the minor 0.6.x releases are dropped, PyWeather 0.7 beta will start development, in which tide and hurricane data will get added, and PWS data in PyWeather 0.7.1 beta. See the full "future of PyWeather" notice in the readme for more.

Enjoy PyWeather 0.6 beta! I'll be taking a 3 week hiatus from Python development, maybe doing some spontaneous development in the mean time. After mid-June, I'll be back to full storm development!

Assets 3
Loading