On Fri, Oct 10, 2008 at 3:34 PM, Arnoud Tijssen <[EMAIL PROTECTED]> wrote: > > I`m using django 1.1 pre-alpha SVN-9218 and according to surftrackr it was > best to use the latest django version from subversion.
It sounds like they need to update either their advice or their code - preferably both :-) Prior to the release of v1.0, it was common to advise people to use the latest SVN release. There was a long break between the 0.96 release and the 1.0 release, and there were a lot of bug fixes and useful features added in that period. However, in the lead up to v1.0, a lot of backwards incompatible changes were made, so advising people to use the latest SVN became a little risky if you weren't keeping your codebase up to date. SVN revision 7970 was the last release that contained newforms; there was a compatibility layer in place until revision 8291. As for how to update the code - that depends. If the developers of surftrackr followed the advice we gave when we introduced newforms, they will have used: from django import newforms as forms throughout their code, in which case, the migration process is as simple as replacing those import statements with: from django import forms However, if they have imported newforms in some other way, you will need to apply different changes. Essentially it's just a name change: any usage of newforms should now refer to forms, but you will need to dig deeper to see if a simple search and replace is all that is required. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
