Start an AppEngine project to track gooseball stats.
Basic Game model
Show LeagueStats on the index page, using Jinja2 templates.
Move models into their own files, one for AppEngine backed models and one for plain Python objects.
Model re-org.
Use a Scraper class to scrape scoreboard data when a URL is hit.
Merge branch 'master' into appengine
Use the Scraper to drive command line parsing.
Change the signature of the scraper to accept date parts (year, month, day) and add a method to break a date down into the relevant date pars.
Factories to create db-backed Game and TeamStat objects from scoreboard data.
Don't create a new Game object if we've already seen the game id before.
Don't keep separate TeamStats in the db, just dump all the stats, home and away, in the Game.
Remove final() check from TeamStats, it doesn't make sense now that TeamStats includes multiple games.
Merge branch 'master' into appengine

Conflicts:
	parse.py
Small bugs in the Game factory.
Use gid as the Game's key, instead of just another property.
Scrape and update stats from the scrape/YYYY/MM/DD URL.
Store just the game date, not a datetime.
Don't bother checking if the game already exists when scraping, AppEngine will just overwrite it.
Add an endpoint that prints stats for a range of dates.