thanks for the reply... adding the empty __init__.py file worked. I like Rubics idea aswell. Importing extra utilities could prove very flexible.
thanks again :) -- stefan On Jan 10, 2007, at 15:54, Nathan R. Yergler wrote: > > Did you add a file named __init__.py to the views directory you > created? > This file tells Python to treat the directory as a package and allow > traversal into the view file. > > NRY > > Stefan Foulis wrote: >> I searched around the django documentation and didn't find anything >> about this... >> >> what I'm trying to do is divide up the views.py file into multiple >> files because the single views.py file in some of my apps is getting >> very cluttered. >> >> I tried just making a views subdirectory and then placing multiple >> files with groups of views inside, referencing to them in urls.py >> with an extra dot with the name... >> >> classic reference: >> ProjectName.AppName.views.functionName (using a single views.py) >> >> then I tried this: >> ProjectName.AppName.views.viewGroupFileName.functionName >> (with a directory called "views" in the Application Directory and a >> python File "viewGroupFileName.py" in there that has a function >> called "functionName" inside) >> >> With this I get a ViewDoesNotExitst: No module named >> viewGroupFileName.functionName. >> >> Is it possible to divide up the view into multiple files? Is this >> also possible with models? >> >> thanks for any hints >> >> - stefan >> >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
