My Django sprint patch has been committed!

Bloody TemplateSyntaxError will now occur only upon... errors... in... the template syntax...

Have you tried to sit down and teach anyone Django lately? Maybe run them through the tutorial?

Have you then watched as they made a slight mistake, including but not limited to: Typing the database host name incorrectly, bugling the queryset syntax, mis-typing the name of a variable in the view, etc? All the while with a perfectly fine template?

....and have you then watched as Django raised TemplateSyntaxError?

This problem was very annoying for us at SlashRoot - it was a major hurdle in making new django developers feel empowered and informed about the state of their app. On a daily basis, one can hear shouts of "but the template looks fine!" coming from our dev stations.

I made this problem my mission at the sprint at Djangocon.us 2011. With a great deal of help from the very patient Carl Meyer, I banged out a fix. You can see the ticket here.

This is SlashRoot's biggest contribution so far to Django, and we're super proud and happy to help.