Friday, October 7, 2011

Re: Easy question (I hope)

On Fri, Oct 7, 2011 at 3:57 PM, Shawn Milochik <shawn@milochik.com> wrote:
> Tom,
> The 'magic' I was referring to was the check for the existence of a
> 'models.py,' thus preventing you from replacing it with a models directory
> containing __init__.py. That's what a Pythonista would normally do in this
> case. That 'magic' requires you to import the things from models.py instead
> of models/__init__.py.
>

I do this a lot, and haven't found any problems with doing so. My main
app has no models.py, but has models/{__init__,foo}.py, and it is
still found quite happily by syncdb, south, the admin interface, the
app template loader etc.

Is there a concrete example of a thing that will not work with this structure?

Cheers

Tom

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment