Glad to hear you got it sorted :-)
Tim ^,^
On Thu, Aug 28, 2008 at 11:29 AM, Ben Eliott <[EMAIL PROTECTED]> wrote:
>
> I found this was caused by redundant non-conventional admin imports
> left over from development in newforms-admin days. There is few days
> difference in my django version o
I found this was caused by redundant non-conventional admin imports
left over from development in newforms-admin days. There is few days
difference in my django version online and offline and the very latest
SVN 1.0-beta decided, rightly, to play havoc with them.
On 27 Aug 2008, at 21:23,
Thank you for coming back on this. Tim - The structure is organised as
you say. James - Thanks for confirming it is simply a path situation,
which is all it could be i guess, but for some reason things haven't
been working out which has been making me think something else might
have been g
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
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"
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 tha
6 matches
Mail list logo
