I'm not sure exactly what you're asking. Maybe you could give a concrete
example. For a complex example, you could take a look at the urls.py for
djangoproject.com:
https://github.com/django/djangoproject.com/blob/249c3482982fc43afc6b6fa575fe79f938ebe472/djangoproject/urls/www.py.
There are
Is there convention on import view as vs a separate URL file in every app?
Is there separate URL in each app only used if you need to use include() ??
On Saturday, August 6, 2016 at 10:05:25 AM UTC-5, Tim Graham wrote:
>
> You're not missing something. You should imports. Sorry you don't like
You're not missing something. You should imports. Sorry you don't like the
look of it, but that's Python.
On Saturday, August 6, 2016 at 8:42:29 AM UTC-4, Andrew Emory wrote:
>
> I am having trouble with how I would intuitively get my url patterns to
> work, by listing the actual path to the
I am having trouble with how I would intuitively get my url patterns to
work, by listing the actual path to the view function.
So it needs to be a callable, ok. But I don't like having 15+ from appname
import views as appname_view.
I can add a url.py file in each app and use include(). But
4 matches
Mail list logo
