website/www/conservancy/apps/events/urls.py
Bradley M. Kuhn f6bbcc7ee3 Just quit it with this relative import stuff.
While I think these relative imports seem to be valid for the running
application, I am having trouble with the django-admin applications
regarding them.  I don't see this syntactic sugar as absolutely
essential, so I'm just going to change it now.
2015-03-08 17:54:05 -07:00

24 lines
909 B
Python

from django.conf.urls import patterns, url, include
from conservancy.apps.events.models import Event
info_dict = {
'queryset': Event.objects.all(),
'date_field': 'date',
'allow_future': True,
}
# FIXME -- see blog and news for examples
# urlpatterns = patterns('django.views.generic.date_based',
# (r'^(?P<year>\d{4})/$', 'archive_year', dict(info_dict,
# make_object_list=True)),
# )
# urlpatterns += patterns('conservancy.apps.events.views',
# (r'^/?$', 'custom_index', dict(info_dict, queryset=Event.past.all(), paginate_by=10)),
# (r'^(?P<year>\d{4})/(?P<slug>[-\w]+)/$', 'event_detail', dict(info_dict, slug_field='slug')),
# (r'^ics/$', 'future_event_ics', info_dict),
# )
urlpatterns = patterns('conservancy.apps.events.views',
(r'^.*$', 'custom_index', dict(info_dict, queryset=Event.past.all(), paginate_by=10)),
)