that's the point On Fri, May 22, 2009 at 4:30 PM, Daniel Roseman < roseman.dan...@googlemail.com> wrote:
> > On May 22, 6:19 am, vishy <vishalsod...@gmail.com> wrote: > > Hi, > > > > I have some functionality which needs to be part of a class,which I > > don't want to persist in database.Where should I put such a class? In > > models.py? > > You can put it anywhere on your pythonpath. If it's related to a > single application, you might try to put it into a lib file or > directory under that app, so you can do 'from myapp.lib import > myclass'. Or, if it's more general, you might have a lib directory at > the same level as the applications, so you would just do 'from lib > import myclass'. Up to you. > -- > DR. > > > --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
