search

TireSwingSoftware / openassign-server

OpenAssign server intended for use by a separate client via RPC
BSD 3-Clause "New" or "Revised" License
6 stars 2 forks source link

Try Django 1.4 #149

Closed mhrivnak closed 12 years ago

mhrivnak commented 12 years ago

Django 1.4 was released a few days ago. We have just enough time before completing this phase of the project to attempt an upgrade. Grab django 1.4, run the tests, and see how it goes. If everything checks out, let's switch ASAP so we can get at least a couple of weeks of using it for development before shipping it.

I just browsed through the list of backward incompatibilities, and I didn't see any that looked like they would matter for us.

https://docs.djangoproject.com/en/dev/releases/1.4/

jc0n commented 12 years ago

The timezone changes seem to break a lot of things. All of the migrations and fixtures will have to be regenerated which is not a problem. Also, every place which uses utcnow() in the code should be changed to timezone aware.

There is another issue which seems that the latest version of south (0.7.4) is required with Django 1.4. See http://south.aeracode.org/ticket/1012.

mhrivnak commented 12 years ago

Did you try setting USE_TZ = False in settings.py? https://docs.djangoproject.com/en/dev/topics/i18n/timezones/#time-zones-migration-guide

I'm happy to upgrade to the latest south. As previously advertised, none of our migrations are currently valuable, so we can blow them away at will.

jc0n commented 12 years ago

Yes. That was the default. I encountered a number of issues with that as well. I also think its probably as good a time as ever to resolve the timezone issues. I think I can do it with relatively minimal effort.