Ya see? I *knew* it was obvious ... as I already had the "Backwards- incompatible changes" page open.
The problem was is that I was convinced it was a unicode-merge issue so I've been up and down http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist and http://www.djangoproject.com/documentation/unicode/ Then I was thinking it might be a render_to_response issue, so I was poring over http://www.djangoproject.com/documentation/shortcuts/ So it's not as if I warn't RTFM'ing, just RTFM'ing in the wrong place(s). Which is why I asked for (and received) a point in the *right* direction. (I'll read all the docs a'fore wondering about how much magic's taking place : ) ) Anyways, *many* thanks James! On Dec 4, 1:04 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 12/4/07, JHeasly <[EMAIL PROTECTED]> wrote: > > > it works as expected. So it seems something in the templating response > > food chain is converting the greater than's/less than's(?). > > > What is the obvious thing I'm missing? > > You're going against the strong recommendation of the Django project, > which is that if you're going to track trunk you should be keeping an > eye on the development process and, at the very least, watching the > list of backwards-incompatible changes which occur between stable > releases; this page will tell you what's going on. > > http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
