Django 1.7 is the first version to have schema migrations built in, thanks to this wonderful kickstarter:<p><a href="https://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django" rel="nofollow">https://www.kickstarter.com/projects/andrewgodwin/schema-mig...</a>
Would anyone who is familiar with both Django and the .js ecosystem care to comment on how they compare? I'm curious to know what how I would find life in the server-side js world. I've not heard of anything in the js ecosystem that's taking on the sort of problems Django tries to solve. (not to say they aren't solving different problems in some better ways)<p>Is it more sensible to regard Django (and Rails and other frameworks from that generation) and the node ecosystem as complementary rather than competitive at this present time? i.e. to use Django for the content-heavy parts and run node alongside it for the more app-like or real-time aspects?<p>And is this likely to change over time?<p>(please - don't let this prompt another micro vs macro framework debate or a discussion on Django being 'too big' - save that for another time)
Can someone familiar with Grails and Django give their 2c? I've done a fair amount of work in Grails, and when I did a small project in Django I found it somewhat more difficult to work with.<p>With Django, the quick test runs and startup were wins (although Grails mitigates that a bit these days), but I thought Django's organization (or lack thereof) was a confusing mess and dealing with forms was an exercise in bending the API instead of working with it.
So, I'm still at 1.4.10 for my startup that's still in private beta. I'm feeling left behind very rapidly. Is the effort to update from 1.4.x to 1.7.x worth it before going public? Also, as a general policy, is it best to always stay one version behind?<p>Is there a good guide for going from 1.4 to 1.6?
This document[1] seems to imply that Django works with Python3 since 1.5. But I don't find mentions of it in the release notes of 1.7b1[2] on the Python Compatibility area.<p>My main interest in porting my 1.3 Django App to a newer version is to get Python 3 support.<p>Does anyone here run Django on Python3 and care to share the experience?<p>[1] <a href="https://docs.djangoproject.com/en/dev/topics/python3/" rel="nofollow">https://docs.djangoproject.com/en/dev/topics/python3/</a><p>[2] <a href="https://docs.djangoproject.com/en/dev/releases/1.7/#python-compatibility" rel="nofollow">https://docs.djangoproject.com/en/dev/releases/1.7/#python-c...</a>
Nice !
Btw, the download link on the page seems broken.
It's going to :
<a href="https://www.djangoproject.com/m/releases/1.7/Django-1.7b2.tar.gz" rel="nofollow">https://www.djangoproject.com/m/releases/1.7/Django-1.7b2.ta...</a><p>while the package is on:
<a href="https://www.djangoproject.com/m/releases/1.7/Django-1.7b1.tar.gz" rel="nofollow">https://www.djangoproject.com/m/releases/1.7/Django-1.7b1.ta...</a>
I was just about to get started learning how to use South migrations. Should I continue, or just focus on the development of the rest of the project while I wait for a stable Django 1.7 to get released? What sort of timeline does its releases usually follow? Is the API fairly consistent with South, seeing as its from the same developer?