-
Notifications
You must be signed in to change notification settings - Fork 8
Updating
PyWeather presently has a few ways to update, and will soon have other ways to update. This document details updating PyWeather through each method, and how it's accomplished.
Starting with 0.2 beta, you've always been able to download a new release on GitHub, with the included .zip.
Updating is simple, unzip the .zip file, and move over your apikey.txt file. Make config changes if needed. It's the simple way to go.
This method gets distributed with config.ini.
Starting with 0.3.1 beta, you could download the latest version of PyWeather in PyWeather, using a .zip file.
Updating goes the same way as it does above, and this method gets distributed with config.ini.
Starting with 0.5.2 beta, users that had Git could use git to update PyWeather. This was done through stashes and checkouts and lots of fun stuff.
In 0.5.2 beta, users are REQUIRED to stash any changes that were made to the config file. As such, the user had to redo any changes made.
Attempts will be made to try and alleviate updating using this method, with a possible configsetup.py script. The default config.ini wouldn't be distributed directly through GitHub (however, a config_NOTINUSE.ini file would get distributed instead), but after a git update, PyWeather would execute this script, updating the config with the latest options, but preserving user preferences.
The nitty-gritty of using this update method isn't 100% sorted, yet. There would have to be a technical implementation to alert users of a non-provisioned config file, and a way to tell if the config file was getting updated for an update, or getting newly provisioned.
Likely coming far off. If this comes to an update, git/.zip downloading would still be supported.
Doing this would add new code to all files, but still not distribute config.ini, still requiring the configsetup.py script. The logistics of doing this haven't been figured out, but it is something that will likely come down the road.