convore.json/groups/django-community/should-django-factor-controllers-out-of-urlspy/messages.json

[{"user_id": 13222, "stars": [], "topic_id": 13639, "date_created": 1300387141.514436, "message": "The amount of arguments to pass to class-based generic views starts to get pretty unrelated to url routing.", "group_id": 81, "id": 376495}, {"user_id": 1167, "stars": [], "topic_id": 13639, "date_created": 1300387336.753207, "message": "You don't *have* to pass arguments to class-based views your urls. I use them in a declarative way in views.py, I even declare view = ViewClass.as_view() at the bottom of the class definition. This way in urls.py you just import & reference the view callable", "group_id": 81, "id": 376522}, {"user_id": 13222, "stars": [], "topic_id": 13639, "date_created": 1300387022.0724411, "message": "Is it just me, or are urlpatterns in urls.py starting to get messy? Are there any efforts to clean this up, and perhaps introduce controllers?", "group_id": 81, "id": 376487}]