Wednesday, July 28, 2010

Re: moving to django 1.2.1

One issue that bit me that has also been mentioned here in other
threads: errors that were previously caught are now raised as errors.
So technically it was wrong previously but functionally it only breaks
on 1.2. I haven't found a good explanation / summary of what/why/
which errors it now affects. Mine was a circular import error that I
had to track down. Important to note -- the error only showed up when
the app ran via wsgi or when I did an import main in the py shell, it
did not throw an error in the dev server!! So do your upgrade testing
accordingly.

Good luck!

D

On Jul 28, 10:03 am, Massimiliano Ravelli
<massimiliano.rave...@gmail.com> wrote:
> On 28 Lug, 15:44, knight <alexar...@gmail.com> wrote:
>
> > Does anybody knows a good post or blog about the changes including
> > csrf?
>
> I forgot to suggest readinghttp://docs.djangoproject.com/en/dev/releases/1.2/#backwards-incompat...

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment