me is that you have to include
the whole views.py in your url conf. Just feels less graceful than
having the dispatcher nab what it needs on demand. I'll get over it.
Unless someone has a better idea!
On Dec 3, 3:12 pm, Daniel Roseman wrote:
> On Dec 3, 8:47 pm, Andrew Willey wrot
Forgot to in mention the actual question from the subject.
Is there a "blessed" way to use class-based views with named urls in
the
> url(r'^location/$', view='WouldLoveToHaveClassBasedView.as_view',
> name='name_for_convenience')
On Dec 3, 1:46 pm
Can someone point me in the right direction here?
How does one use class-based generic views and named URLs?
Example (doesn't work):
> urls.py
> urlpatterns += patterns('myapp.views',
>(r'^location/$', MyGenericView.as_view()),
> )
> views.py
> class MyGenericView(TemplateView):
>templa
3 matches
Mail list logo
