merge latest master changes into Eli's branch

WIP merge from Master into sideboard-sqlalchemy, so that Vicki and Dom's changes can make it into ubersystem 2.0

(People might call me crazy, but p4merge (perforce) is still a great tool for these tricky 3-way merges.)

Eli, I -think- I did all the unpleasant work for this and you might be OK to pull this into your branch and see what happens.  There are some issues to be addressed which I've outlined here:
https://docs.google.com/document/d/1p0AReHCmCatfp0GwTbilvovIZSc6fjKZIWPxKSiVINY/edit

I propose after your branch is ready to go, we rename 'master' to 'uber1-master' and make your branch the master.

For 8.5 we should stick with uber1, and for 13 we should go with uber2 here.  After 8.5 is done, uber1 goes away.

All 8.5 changes at this point should be pretty minor little bugfixes here and there.  Eli, big merges suck, so if you can, from this stage on, let's try and keep the changes from master into this sideboard branch so that when it's time to roll out m13, it's not a big deal.
you sure? I can imagine running a magfest event in a different timezone : )
   Kinda planning on it someday : )


On Mon, Jul 7, 2014 at 3:44 PM, Eli Courtwright <notifications@github.com>
wrote:

> In uber/models.py:
>
> > @@ -451,6 +452,9 @@ def _misc_adjustments(self):
> >              if value.isupper() or value.islower():
> >                  setattr(self, attr, value.title())
> >
> > +        if not self.registered:
>
> Correct; this can be removed. Also in the future we can no longer use bare
> datetime objects, since I've updated Uber to be timezone-aware and added
> an EVENT_TIMEZONE config option. Which was probably a waste of time, since
> I can't imagine we'd ever consider running a MAGFest event in a different
> timezone... :P
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/magfest/ubersystem/pull/339/files#r14617656>.
>