Karen, thank you for your thorough response. It gives me a direction and food for thought.
Tonu Karen Tracey wrote: > On Wed, Oct 8, 2008 at 2:50 PM, Tonu Mikk <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Here is a bit more info on the error that I am getting with > OpenBookPlatform. > > When I try to access booklist in OpenBookPlatform I received this > error: > Exception Value: Could not import apps.books.views. Error was: cannot > import name validators > > Same error appears when I try to use the Register link: > Exception Value: Could not import apps.users.views.auth. Error was: > cannot import name validators > > I suspect that I am receiving this error because OpenBookPlatform was > created in Django version 0.97 and it seems that the django validators > have changes sufficiently between 1.0 and previous versions. > I see a line in views.py: from django.core import validators . I am > wondering if I need to be using a different string here? > > Thank you, > Tonu > > Tonu Mikk wrote: > > Hello, I wonder if anyone has tried porting the OpenBookPlatform > > http://djangosites.org/s/limodou-51boo-com/ to Django v1? I am > trying > > this, but running into problems. I contacted the project owner, > but he > > is not maintaining the code any more. > > > > > Taking a look at the change history for this project: > > http://code.google.com/p/openbookplatform/source/list > > shows that the last code change was made over a year ago. There were > a lot of backwards-incompatible changes made in Django over the last > year (fully documented on the backwards-incompatible page and the 1.0 > porting guide). It is not going to be as simple as fixing this one > import that is no longer working. Since the original owner is no > longer maintaining the code, you've got to decide whether you want to > port the existing code to 1.0 yourself or start afresh (I have never > heard of this project before so have no idea what it does or how big > it is). > > If I were you I'd start with a quick evaluation of the existing code > to determine if you think it is worth the porting effort. Porting > code you've written yourself from 0.96 to 1.0 is not particularly hard > since one can generally recall while reading through the > backwards-incompatible list "oh yeah I used that somewhere I > think"...porting someone else's code from that uses old constructs > never learned is a bit more of a chore. > > To answer the specific question about this import, validators are no > more, so there is no 'just change x to y' fix for this. You'll need > to figure out what they were being used for (maybe they were tied into > some use of old forms/manipulators which I never used so I'm fuzzy on > them) and come up with a 1.0 replacement. Newforms (now forms in > Django 1.0) has an entirely different way of doing form validation. > > Karen > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
