Make the structer sitedir (manage.py urls.py,settings.py)->app(models.py views.py....) And import it accordingly If your code is running in the sitedir then it should be able to import it.
On Wed, Aug 27, 2008 at 12:34 PM, Tim Kersten <[EMAIL PROTECTED]> wrote: > > Your app folder must be in the current directory, iirc, or in the > python path for the import to work. Because the project is in the > python path you'll always be able to import project.app. Rather than > trying to "import something from app" - which as you said fails, you > could try "import something", as long as your script is in the same > folder. > > I'm not sure the above works as I'm writing from memory. > > Tim ^,^ > > > > > On Wed, Aug 27, 2008 at 7:49 PM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: >> >> All apps works fine in the local development environment, upload it to >> the server run syncdb and bang! import conflicts all over the place >> 'cannot import xxx'. Django apps and standalone apps are fine, it's >> only with the import statements amongst inter-related models in the >> project's own apps that the trouble begins. I'm using django SVN and >> postgresql 8.3.3. >> >> I'm sure there is some real simple noobie answer probably related to >> the pythonpath here i've missed. >> >> The actual import statements refer only to the app ( ie. 'from app >> import model', rather than 'from project.app import model'.) Adding >> the project name to the statements does solve this. But what's the >> cleaner one-stop path solution? >> >> Thanks in advance. >> >> >> > >> > > > > -- http://www.goldwatches.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
